CVE-2024-55885: medium-severity vulnerability in beego
Beego Vulnerable to Collision Hazards of MD5 in Cache Key Filenames
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
No sign of exploitation. No public exploitation artifact known so far.
Beego web framework uses MD5 to generate cache filenames, which is cryptographically weak and vulnerable to collision attacks. This could allow attackers to manipulate cache data and potentially compromise application behavior.
Beego versions prior to 2.3.4 employ MD5 hashing for cache key filenames (CWE-327, CWE-328), enabling collision attacks where adversaries craft inputs that generate identical MD5 hashes, potentially overwriting or poisoning cached content. The attack vector requires influencing cache input data; impact includes cache manipulation and application logic bypass. Version 2.3.4 mitigates this by replacing MD5 with SHA256.
In the same product, most dangerous first.