Skip to content

Commit 18ef76e

Browse files
committed
GHSA SYNC: 1 brand new advisory
1 parent 161d6cf commit 18ef76e

File tree

1 file changed

+29
-13
lines changed

1 file changed

+29
-13
lines changed

gems/activesupport/CVE-2023-38037.yml

Lines changed: 29 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -7,31 +7,47 @@ url: https://github.com/rails/rails/releases/tag/v7.0.7.1
77
title: Possible File Disclosure of Locally Encrypted Files
88
date: 2023-08-23
99
description: |
10-
There is a possible file disclosure of locally encrypted files in Active Support. This vulnerability has been assigned the CVE identifier CVE-2023-38037.
10+
There is a possible file disclosure of locally encrypted files in
11+
Active Support. This vulnerability has been assigned the
12+
CVE identifier CVE-2023-38037.
1113
12-
Versions Affected: >= 5.2.0 Not affected: < 5.2.0 Fixed Versions: 7.0.7.1, 6.1.7.5
14+
* Versions Affected: >= 5.2.0
15+
* Not affected: < 5.2.0
16+
* Fixed Versions: 7.0.7.1, 6.1.7.5
1317
1418
# Impact
15-
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.
1619
17-
Attackers that have access to the file system could possibly read the contents of this temporary file while a user is editing it.
20+
ActiveSupport::EncryptedFile writes contents that will be encrypted
21+
to a temporary file. The temporary file’s permissions are defaulted
22+
to the user’s current umask settings, meaning that it’s possible
23+
for other users on the same system to read the contents of the
24+
temporary file.
1825
19-
All users running an affected release should either upgrade or use one of the workarounds immediately.
26+
Attackers that have access to the file system could possibly read
27+
the contents of this temporary file while a user is editing it.
28+
29+
All users running an affected release should either upgrade or use
30+
one of the workarounds immediately.
2031
2132
# Releases
33+
2234
The fixed releases are available at the normal locations.
2335
2436
# Workarounds
25-
To work around this issue, you can set your umask to be more restrictive like this:
2637
27-
```ruby
28-
$ umask 0077
29-
```
38+
To work around this issue, you can set your umask to be more
39+
restrictive like this:
40+
41+
$ umask 0077
42+
cvss_v3: 5.5
3043
unaffected_versions:
31-
- "< 5.2.0"
44+
- "< 5.2.0"
3245
patched_versions:
33-
- "~> 6.1.7, >= 6.1.7.5"
34-
- ">= 7.0.7.1"
46+
- "~> 6.1.7, >= 6.1.7.5"
47+
- ">= 7.0.7.1"
3548
related:
3649
url:
37-
- https://github.com/rails/rails/commit/a21d6edf35a60383dfa6c4da49e4b1aef5f00731
50+
- https://nvd.nist.gov/vuln/detail/CVE-2023-38037
51+
- https://github.com/rails/rails/releases/tag/v7.0.7.1
52+
- https://github.com/rails/rails/commit/a21d6edf35a60383dfa6c4da49e4b1aef5f00731
53+
- https://github.com/advisories/GHSA-cr5q-6q9f-rq6q

0 commit comments

Comments
 (0)