CVE-2024-24564 json
Vyper extract32 can ready dirty memory
published 2y ago modified 4mo ago also EUVD-2024-0181 , GHSA-4hwq-4cpm-8vmx , PYSEC-2024-205
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. When using the built-in `extract32(b, start)`, if the `start` index provided has for side effect to update `b`, the byte array to extract `32` bytes from, it could be that some dirty memory is read and returned by `extract32`. This vulnerability is fixed in 0.4.0.
Patch / fix
Is CVE-2024-24564 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/vyperlang/vyper/security/advisories/GHSA-4hwq-4cpm-8vmx referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| OSV | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | vyper | <0.4.0 |
0.4.0 |
Affected products
- vyperlang vyper
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/vyperlang/vyper/commit/3d9c537142fb99b2672f21e2057f5f202cde194f
web, patch
-
github.com
/vyperlang/vyper/security/advisories/GHSA-4hwq-4cpm-8vmx
web, exploit, vendor-advisory, advisory, evidence
-
nvd.nist.gov
/vuln/detail/CVE-2024-24564
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2024-205.yaml
web
-
github.com
/vyperlang/vyper
package
-
github.com
/vyperlang/vyper/blob/10564dcc37756f3d3684b7a91fd8f4325a38c4d8/vyper/builtins/functions.py#L916-L918
web
-
github.com
/vyperlang/vyper/blob/10564dcc37756f3d3684b7a91fd8f4325a38c4d8/vyper/builtins/functions.py#L920-L922
web
-
github.com
/advisories/GHSA-4hwq-4cpm-8vmx
advisory
Sources
- CVE List CVE-2024-24564
- GitHub Advisory GHSA-4hwq-4cpm-8vmx
- NVD CVE-2024-24564
- OSV PYSEC-2024-205
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.