Loading HuntDB...
Hunt
Vulnerability Intelligence by wss.sh
Home Daily Briefings High Impact CVEs Recent Exploits KEV Catalog GitHub Advisories Latest Updates Security News
Sign In Sign Up

CVE-2024-32645

MEDIUM
Published 2024-04-25T17:18:27.026Z
Actions:

Expert Analysis

Professional remediation guidance

Get tailored security recommendations from our analyst team for CVE-2024-32645. We'll provide specific mitigation strategies based on your environment and risk profile.

CVSS Score

V3.1
5.3
/10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Base Score Metrics
Exploitability: N/A Impact: N/A

EPSS Score

v2023.03.01
0.000
probability
of exploitation in the wild

There is a 0.0% chance that this vulnerability will be exploited in the wild within the next 30 days.

Updated: 2025-01-25
Exploit Probability
Percentile: 0.193
Higher than 19.3% of all CVEs

Attack Vector Metrics

Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED

Impact Metrics

Confidentiality
NONE
Integrity
LOW
Availability
NONE

Description

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.

Available Exploits

No exploits available for this CVE.

Related News

No news articles found for this CVE.

Affected Products

vyperlang

vyper

Affected Versions:

<= 0.3.10
vyperlang

vyper

Affected Versions:

0

GitHub Security Advisories

Community-driven vulnerability intelligence from GitHub

✓ GitHub Reviewed MODERATE

vyper performs incorrect topic logging in raw_log

GHSA-xchq-w5r3-4wg3

Advisory Details

### Summary 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. In particular, no uses of `raw_log()` were found at all in production; it is apparently not a well-known function. ### Details The `build_IR` function of the `RawLog` class fails to properly unwrap the variables provided as topics. Consequently, incorrect values are logged as topics. ### PoC ```vyper x: bytes32 @external def f(): self.x = 0x1234567890123456789012345678901234567890123456789012345678901234 raw_log([self.x], b"") # LOG1(offset:0x60, size:0x00, topic1:0x00) y: bytes32 = 0x1234567890123456789012345678901234567890123456789012345678901234 raw_log([y], b"") # LOG1(offset:0x80, size:0x00, topic1:0x40) ``` ### Patches Fixed in https://github.com/vyperlang/vyper/pull/3977. ### Impact Incorrect values can be logged which may result in unexpected behavior in client-side applications relying on these logs.

Affected Packages

PyPI vyper
ECOSYSTEM: ≥0 <0.4.0

CVSS Scoring

CVSS Score

5.0

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

WEB https://github.com/vyperlang/vyper/security/advisories/GHSA-xchq-w5r3-4wg3
ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2024-32645
WEB https://github.com/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2024-206.yaml
PACKAGE https://github.com/vyperlang/vyper

Advisory provided by GitHub Security Advisory Database. Published: April 25, 2024, Modified: January 21, 2025

References

https://github.com/vyperlang/vyper/security/advisories/GHSA-xchq-w5r3-4wg3
Published: 2024-04-25T17:18:27.026Z
Last Modified: 2024-08-02T02:13:40.291Z
Copied to clipboard!