CVE-2024-32645

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 28% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. In versions 0.3.10 and prior, incorrect values can be logged when raw_log builtin is called with memory or storage arguments to be used as topics. A contract search was performed and no vulnerable contracts were found in production. The build_IR function of the RawLog class fails to properly unwrap the variables provided as topics. Consequently, incorrect values are logged as topics. As of time of publication, no fixed version is available.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
36.3%
KEV
Not listed

Published

April 25, 2024

Last Modified

January 2, 2025

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
vyper0.1.0b1 ... 0.4.0rc6 (61 versions)0.4.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Frequently asked(5)

What is CVE-2024-32645?
CVE-2024-32645 is a medium vulnerability published on April 25, 2024. Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. In versions 0.3.10 and prior, incorrect values can be logged when rawlog builtin is called with memory or storage arguments to be used as topics. A contract search was performed and no vulnerable contracts were found in…
When was CVE-2024-32645 disclosed?
CVE-2024-32645 was first published in the National Vulnerability Database on April 25, 2024, with the most recent update on January 2, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-32645 actively exploited?
CVE-2024-32645 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-32645?
CVE-2024-32645 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2024-32645?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-32645, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-32645

Explore →

Is Your Infrastructure Affected by CVE-2024-32645?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.