Headline
Red Hat Security Advisory 2023-7720-03
Red Hat Security Advisory 2023-7720-03 - An update is now available for RHOL-5.8-RHEL-9. Issues addressed include a file disclosure vulnerability.
The following advisory data is extracted from:https://access.redhat.com/security/data/csaf/v2/advisories/2023/rhsa-2023_7720.jsonRed Hat officially shut down their mailing list notifications October 10, 2023. Due to this, Packet Storm has recreated the below data as a reference point to raise awareness. It must be noted that due to an inability to easily track revision updates without crawling Red Hat's archive, these advisories are single notifications and we strongly suggest that you visit the Red Hat provided links to ensure you have the latest information available if the subject matter listed pertains to your environment.- Packet Storm Staff====================================================================Red Hat Security AdvisorySynopsis: Low: Logging Subsystem 5.8.1- Red Hat OpenShift security updateAdvisory ID: RHSA-2023:7720-03Product: Logging Subsystem for Red Hat OpenShiftAdvisory URL: https://access.redhat.com/errata/RHSA-2023:7720Issue date: 2023-12-13Revision: 03CVE Names: CVE-2023-38037====================================================================Summary: An update is now available for RHOL-5.8-RHEL-9.Red Hat Product Security has rated this update as having a security impact of Low. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.Description:Logging Subsystem 5.8.1- Red Hat OpenShiftSecurity Fix(es):* rubygem-activesupport: File Disclosure of Locally Encrypted Files (CVE-2023-38037)For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.Solution:https://access.redhat.com/articles/11258CVEs:CVE-2023-38037References:https://access.redhat.com/security/updates/classification/#lowhttps://bugzilla.redhat.com/show_bug.cgi?id=2236261https://issues.redhat.com/browse/LOG-4452https://issues.redhat.com/browse/LOG-4480https://issues.redhat.com/browse/LOG-4612https://issues.redhat.com/browse/LOG-4655https://issues.redhat.com/browse/LOG-4683https://issues.redhat.com/browse/LOG-4706https://issues.redhat.com/browse/LOG-4741https://issues.redhat.com/browse/LOG-4768https://issues.redhat.com/browse/LOG-4780https://issues.redhat.com/browse/LOG-4791https://issues.redhat.com/browse/LOG-4811https://issues.redhat.com/browse/LOG-4815https://issues.redhat.com/browse/LOG-4821https://issues.redhat.com/browse/LOG-4828https://issues.redhat.com/browse/LOG-4836https://issues.redhat.com/browse/LOG-4841https://issues.redhat.com/browse/LOG-4852Related news
Red Hat Security Advisory 2024-2010-03 - An update is now available for Red Hat Satellite 6.15. The release contains a new version of Satellite and important security fixes for various components. Issues addressed include HTTP request smuggling, crlf injection, denial of service, file disclosure, and traversal vulnerabilities.
Red Hat OpenShift security update. Issues addressed include a file disclosure vulnerability.
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: ```ruby $ umask 0077 ```