Proxy credential theft via delayed permission restriction
Published Apr 9, 2024 · Updated Aug 2, 2024
Credential exposure in DIRAC before 8.0.41 allows local users to read a generated proxy file and assume its delegated privileges. Proxy-writing routines create or truncate the destination under the process umask, write the proxy contents, and only afterward restrict the file to mode 0600. A user with access to the same host must win the sub-millisecond creation window; a successful read permits every action authorized by the original proxy.
Summary
What happened
Credential exposure in DIRAC before 8.0.41 allows local users to read a generated proxy file and assume its delegated privileges. Proxy-writing routines create or truncate the destination under the process umask, write the proxy contents, and only afterward restrict the file to mode 0600. A user with access to the same host must win the sub-millisecond creation window; a successful read permits every action authorized by the original proxy.
The record
- CVE
- CVE-2024-29905
- Published
- Apr 9, 2024
- Updated
- Aug 2, 2024
- Vendor
- DIRACGrid
- Product
- DIRAC
- Classifications
- CWE-668, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 9, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 8.0.41
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo