Vulnerability advisory

GHSA-cr5q-6q9f-rq6q

Active Support Possibly Discloses Locally Encrypted Files

Published Aug 23, 2023Updated Sep 10, 2026OSV record ↗

Also known as CVE-2023-38037

Severity

CVSS 3.xCVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L

Affected versions

activesupport RubyGems

All activesupport advisories →

Affected	Fixed in
`5.2.0` to before 6.1.7.5	`6.1.7.5`Advisories →
Also listed as affected (87) `5.2.0` `5.2.1` `5.2.1.1` `5.2.1.rc1` `5.2.2` `5.2.2.1` `5.2.2.rc1` `5.2.3` `5.2.3.rc1` `5.2.4` `5.2.4.1` `5.2.4.2` `5.2.4.3` `5.2.4.4` `5.2.4.5` `5.2.4.6` `5.2.4.rc1` `5.2.5` `5.2.6` `5.2.6.1` `5.2.6.2` `5.2.6.3` `5.2.7` `5.2.7.1` `5.2.8` `5.2.8.1` `6.0.0` `6.0.0.beta1` `6.0.0.beta2` `6.0.0.beta3` `6.0.0.rc1` `6.0.0.rc2` `6.0.1` `6.0.1.rc1` `6.0.2` `6.0.2.1` `6.0.2.2` `6.0.2.rc1` `6.0.2.rc2` `6.0.3` `6.0.3.1` `6.0.3.2` `6.0.3.3` `6.0.3.4` `6.0.3.5` `6.0.3.6` `6.0.3.7` `6.0.3.rc1` `6.0.4` `6.0.4.1` `6.0.4.2` `6.0.4.3` `6.0.4.4` `6.0.4.5` `6.0.4.6` `6.0.4.7` `6.0.4.8` `6.0.5` `6.0.5.1` `6.0.6` `6.0.6.1` `6.1.0` `6.1.0.rc1` `6.1.0.rc2` `6.1.1` `6.1.2` `6.1.2.1` `6.1.3` `6.1.3.1` `6.1.3.2` `6.1.4` `6.1.4.1` `6.1.4.2` `6.1.4.3` `6.1.4.4` `6.1.4.5` `6.1.4.6` `6.1.4.7` `6.1.5` `6.1.5.1` `6.1.6` `6.1.6.1` `6.1.7` `6.1.7.1` `6.1.7.2` `6.1.7.3` `6.1.7.4`
`7.0.0` to before 7.0.7.1	`7.0.7.1`Advisories →
Also listed as affected (17) `7.0.0` `7.0.1` `7.0.2` `7.0.2.1` `7.0.2.2` `7.0.2.3` `7.0.2.4` `7.0.3` `7.0.3.1` `7.0.4` `7.0.4.1` `7.0.4.2` `7.0.4.3` `7.0.5` `7.0.5.1` `7.0.6` `7.0.7`

Description

There is a possible file disclosure of locally encrypted files in Active Support. This vulnerability has been assigned the CVE identifier CVE-2023-38037.

Versions Affected: >= 5.2.0 Not affected: < 5.2.0 Fixed Versions: 7.0.7.1, 6.1.7.5

Impact

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.

Attackers that have access to the file system could possibly read the contents of this temporary file while a user is editing it.

All users running an affected release should either upgrade or use one of the workarounds immediately.

Releases

The fixed releases are available at the normal locations.

Workarounds

To work around this issue, you can set your umask to be more restrictive like this:

$ umask 0077