You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: advisories/_posts/2023-08-23-CVE-2023-38037.md
+25-9
Original file line number
Diff line number
Diff line change
@@ -15,32 +15,48 @@ advisory:
15
15
title: Possible File Disclosure of Locally Encrypted Files
16
16
date: 2023-08-23
17
17
description: |
18
-
There is a possible file disclosure of locally encrypted files in Active Support. This vulnerability has been assigned the CVE identifier CVE-2023-38037.
18
+
There is a possible file disclosure of locally encrypted files in
19
+
Active Support. This vulnerability has been assigned the
ActiveSupport::EncryptedFile writes contents that will be encrypted to a temporary file. The temporary file’s permissions are defaulted to the user’s current umask settings, meaning that it’s possible for other users on the same system to read the contents of the temporary file.
24
27
25
-
Attackers that have access to the file system could possibly read the contents of this temporary file while a user is editing it.
28
+
ActiveSupport::EncryptedFile writes contents that will be encrypted
29
+
to a temporary file. The temporary file’s permissions are defaulted
30
+
to the user’s current umask settings, meaning that it’s possible
31
+
for other users on the same system to read the contents of the
32
+
temporary file.
26
33
27
-
All users running an affected release should either upgrade or use one of the workarounds immediately.
34
+
Attackers that have access to the file system could possibly read
35
+
the contents of this temporary file while a user is editing it.
36
+
37
+
All users running an affected release should either upgrade or use
38
+
one of the workarounds immediately.
28
39
29
40
# Releases
41
+
30
42
The fixed releases are available at the normal locations.
31
43
32
44
# Workarounds
33
-
To work around this issue, you can set your umask to be more restrictive like this:
34
45
35
-
```ruby
36
-
$ umask 0077
37
-
```
46
+
To work around this issue, you can set your umask to be more
0 commit comments