pysec-2024-148
Vulnerability from pysec
Published
2024-02-02 17:15
Modified
2024-11-21 14:23
Severity ?
Details
Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. When calls to external contracts are made, we write the input buffer starting at byte 28, and allocate the return buffer to start at byte 0 (overlapping with the input buffer). When checking RETURNDATASIZE for dynamic types, the size is compared only to the minimum allowed size for that type, and not to the returned value's length. As a result, malformed return data can cause the contract to mistake data from the input buffer for returndata. When the called contract returns invalid ABIv2 encoded data, the calling contract can read different invalid data (from the dirty buffer) than the called contract returned.
Aliases
{ "affected": [ { "package": { "ecosystem": "PyPI", "name": "vyper", "purl": "pkg:pypi/vyper" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "0.4.0b1" } ], "type": "ECOSYSTEM" } ], "versions": [ "0.1.0b1", "0.1.0b10", "0.1.0b11", "0.1.0b12", "0.1.0b13", "0.1.0b14", "0.1.0b15", "0.1.0b16", "0.1.0b17", "0.1.0b2", "0.1.0b3", "0.1.0b4", "0.1.0b5", "0.1.0b6", "0.1.0b7", "0.1.0b8", "0.1.0b9", "0.2.1", "0.2.10", "0.2.11", "0.2.12", "0.2.13", "0.2.14", "0.2.15", "0.2.16", "0.2.2", "0.2.3", "0.2.4", "0.2.5", "0.2.6", "0.2.7", "0.2.8", "0.2.9", "0.3.0", "0.3.1", "0.3.10", "0.3.10rc1", "0.3.10rc2", "0.3.10rc3", "0.3.10rc4", "0.3.10rc5", "0.3.2", "0.3.3", "0.3.4", "0.3.5", "0.3.6", "0.3.7", "0.3.8", "0.3.9" ] } ], "aliases": [ "CVE-2024-24560", "GHSA-gp3w-2v2m-p686" ], "details": "Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. When calls to external contracts are made, we write the input buffer starting at byte 28, and allocate the return buffer to start at byte 0 (overlapping with the input buffer). When checking RETURNDATASIZE for dynamic types, the size is compared only to the minimum allowed size for that type, and not to the returned value\u0027s length. As a result, malformed return data can cause the contract to mistake data from the input buffer for returndata. When the called contract returns invalid ABIv2 encoded data, the calling contract can read different invalid data (from the dirty buffer) than the called contract returned.", "id": "PYSEC-2024-148", "modified": "2024-11-21T14:23:02.917464+00:00", "published": "2024-02-02T17:15:00+00:00", "references": [ { "type": "EVIDENCE", "url": "https://github.com/vyperlang/vyper/security/advisories/GHSA-gp3w-2v2m-p686" }, { "type": "ADVISORY", "url": "https://github.com/vyperlang/vyper/security/advisories/GHSA-gp3w-2v2m-p686" } ], "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "type": "CVSS_V3" } ] }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.