CVE-2024-55885: Github.com/beego/beego Beego Has Collision Hazards Of Vulnerability
MODERATECVE-2024-55885 is a MODERATE beego has collision hazards of vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Github.com/beego/beego libraries in the Go ecosystem. The issue involves beego has collision hazards of md5 in cache key filenames. Remediation is available by upgrading affected packages to version 2.3.4.
CVE-2024-55885 at a Glance
How to Fix CVE-2024-55885
To remediate this vulnerability, upgrade all affected Github.com/beego/beego dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/beego/beego to Latest secure release
Upgrade github.com/beego/beego/v2 to 2.3.4
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/beego/beego
How to Check if You Are Affected
To determine whether your application is affected by CVE-2024-55885, inspect your project dependencies for Github.com/beego/beego:
inspect dependencies for github.com/beego/beego
Analyze the terminal output to locate any version of Github.com/beego/beego in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.3.4), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In Github.com/beego/beego, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2024-55885 Affected Github.com/beego/beego Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/beego/beego
|
Go |
≤ 1.12.14
|
|
|
github.com/beego/beego/v2
|
Go |
< 2.3.4
|
2.3.4
|
References
Frequently Asked Questions
What is CVE-2024-55885?
Which Github.com/beego/beego versions are affected?
What version fixes CVE-2024-55885?
Is github.com/beego/beego affected?
Is github.com/beego/beego/v2 affected?
What CWE is associated with CVE-2024-55885?
How can I check Go dependencies for CVE-2024-55885?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-9j3m-fr7q-jxfw",
"modified" : "2024-12-18T19:22:40Z",
"published" : "2024-12-12T19:22:39Z",
"aliases" : [ "CVE-2024-55885" ],
"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.\n\n### Understanding Collisions\nA 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.\n\n### Implications for Cache Systems\nIn a cache system where filenames are derived from the MD5 hash of cache keys, a collision could lead to several critical issues:\n\nData 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.\nSecurity 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.\n\nUnpredictable 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.\n\n### Mitigation Strategies\nTo mitigate these risks, consider the following strategies:\n\nUse 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.\n\ncode at:https://github.com/beego/beego/blob/bb72dc27ac3970e51d38ee52fc3dc1465ae25b9d/client/cache/file.go#L126",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/beego/beego"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.12.14"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/beego/beego/v2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.3.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/beego/beego/security/advisories/GHSA-9j3m-fr7q-jxfw"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-55885"
}, {
"type" : "WEB",
"url" : "https://github.com/beego/beego/commit/e7fa4835f71f47ab1d13afd638cebf661800d5a4"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/beego/beego"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-327", "CWE-328" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2024-12-12T19:22:39Z",
"nvd_published_at" : "2024-12-12T20:15:21Z"
}
}