Advisory

GHSA-9j3m-fr7q-jxfw

Also known as: CVE-2024-55885, GO-2024-3331

Summary

Beego has Collision Hazards of MD5 in Cache Key Filenames

Details

In the context of using MD5 to generate filenames for cache keys, there are significant collision hazards that need to be considered. MD5, or Message Digest Algorithm 5, is a widely known cryptographic hash function that produces a 128-bit hash value. However, MD5 is no longer considered secure against well-funded opponents due to its vulnerability to collision attacks.

Understanding Collisions
A collision in hashing occurs when two different inputs produce the same hash output. For MD5, this means that it is theoretically possible, and even practical, to find two distinct cache keys that result in the same MD5 hash. This vulnerability has been well-documented and exploited in various security contexts.

Implications for Cache Systems
In a cache system where filenames are derived from the MD5 hash of cache keys, a collision could lead to several critical issues:

Data Integrity Risks: If two different keys collide, they will map to the same filename. This could result in data being overwritten incorrectly, leading to data loss or corruption.
Security Vulnerabilities: An attacker could potentially exploit collisions to manipulate cache data. For instance, by crafting a key that collides with another key, an attacker might gain unauthorized access to sensitive cached information or inject malicious data.

Unpredictable Behavior: Collisions can cause the cache system to behave unpredictably, as it may retrieve or store data in unintended files, leading to system instability or incorrect behavior.

Mitigation Strategies
To mitigate these risks, consider the following strategies:

Use a More Secure Hash Function: Replace MD5 with a more secure hash function like SHA-256, which has a significantly lower probability of collisions and is resistant to known attack vectors.

code at:https://github.com/beego/beego/blob/bb72dc27ac3970e51d38ee52fc3dc1465ae25b9d/client/cache/file.go#L126

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-12-12 19:22 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/beego/beego

Go · All systems

Affected

  • introduced 0, last affected 1.12.14 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/beego/beego/v2

Go · All systems

Affected

  • introduced 0, fixed 2.3.4 (semver)

Fixed versions

2.3.4

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences