Privilege escalation via MD5 cache filename collisions
Published Jul 31, 2024 · Updated Aug 2, 2024
Weak-hash use in Beego 2.2.0 and earlier allows remote authenticated users to escalate privileges through cache filename collisions. The getCacheFileName function in client/cache/file.go derives cache paths with collision-prone MD5, allowing crafted keys or uploaded files to select the same cache filename. Low-privilege access and an application path accepting attacker-controlled file or cache input are required; successful exploitation can execute code with elevated privileges.
Summary
What happened
Weak-hash use in Beego 2.2.0 and earlier allows remote authenticated users to escalate privileges through cache filename collisions. The getCacheFileName function in client/cache/file.go derives cache paths with collision-prone MD5, allowing crafted keys or uploaded files to select the same cache filename. Low-privilege access and an application path accepting attacker-controlled file or cache input are required; successful exploitation can execute code with elevated privileges.
The record
- CVE
- CVE-2024-40465
- Published
- Jul 31, 2024
- Updated
- Aug 2, 2024
- Vendor
- Beego
- Product
- Beego
- Classifications
- CWE-328, CWE-327, T1068, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 31, 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=0 <=2.2.0
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