CVE-2024-55885: GO-2024-3331 - Beego has Collision Hazards of MD5 in Cache Key Filenames in github.com/beego/beego

CVE-2024-55885 · Severity: medium · CVSS 4 · Published 2024-12-18

Beego has Collision Hazards of MD5 in Cache Key Filenames in github.com/beego/beego

Technologies: github.com/beego/beego (Go), github.com/beego/beego/v2 (Go). Vendors: Go.

Quick answers

Is CVE-2024-55885 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2024-55885 being exploited in the wild.
How severe is CVE-2024-55885?
Medium severity, with a CVSS score of 4, published 18 December 2024.
Which products and versions are affected?
github.com/beego/beego (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.12.14; github.com/beego/beego/v2 (Go) SEMVER:introduced=0,fixed=2.3.4.
Is there a fix for CVE-2024-55885?
Yes. github.com/beego/beego/v2 (Go): upgrade to 2.3.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2024-55885?
Check whether you run github.com/beego/beego (Go) or github.com/beego/beego/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/beego/beego/v2 (Go): upgrade to 2.3.4 or later
    go get github.com/beego/beego/v2@v2.3.4

Affected products

  • github.com/beego/beego (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.12.14
  • github.com/beego/beego/v2 (Go) SEMVER:introduced=0,fixed=2.3.4

Identifiers

  • CVE-2024-55885
  • GHSA-9j3m-fr7q-jxfw
  • GO-2024-3331

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.