Cache data manipulation via MD5 filename collisions
Published Dec 12, 2024 · Updated Dec 13, 2024
Weak hashing in Beego's file-cache filename generation before 2.3.4 allows remote attackers to manipulate cached data via colliding keys. FileCache.getCacheFileName hashes each key with MD5 and uses the digest as its storage path, so distinct colliding keys address the same cache file. Exploitation requires a Beego application to use the file-cache backend with attacker-influenced keys; a collision can overwrite data or return the wrong entry.
Summary
What happened
Weak hashing in Beego's file-cache filename generation before 2.3.4 allows remote attackers to manipulate cached data via colliding keys. FileCache.getCacheFileName hashes each key with MD5 and uses the digest as its storage path, so distinct colliding keys address the same cache file. Exploitation requires a Beego application to use the file-cache backend with attacker-influenced keys; a collision can overwrite data or return the wrong entry.
The record
- CVE
- CVE-2024-55885
- Published
- Dec 12, 2024
- Updated
- Dec 13, 2024
- Vendor
- Beego
- Product
- Beego
- Classifications
- CWE-328, CWE-327, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2024CVE publishedPublication date reported by the CVE source.
- Dec 13, 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=< 2.3.4
What conditions does exploitation require?
What is affected?
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