CVE-2022-24787
published 2022-04-04CVE-2022-24787: Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. In version 0.3.1 and prior, bytestrings can have dirty bytes in them, resulting…
PriorityP340high7.5CVSS 3.1
AVNACLPRNUINSUCNIHAN
EPSS
0.97%
57.9th percentile
Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. In version 0.3.1 and prior, bytestrings can have dirty bytes in them, resulting in the word-for-word comparisons giving incorrect results. Even without dirty nonzero bytes, two bytestrings can compare to equal if one ends with `"\x00"` because there is no comparison of the length. A patch is available and expected to be part of the 0.3.2 release. There are currently no known workarounds.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| vyperlang | vyper | <= 0.3.1 | — |
| vyperlang | vyper | >= 0 < 2c73f8352635c0a433423a5b94740de1a118e508 | 2c73f8352635c0a433423a5b94740de1a118e508 |
| vyperlang | vyper | >= 0 < 0.3.2 | 0.3.2 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2022-24787: Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine
osv·2022-04-04
CVE-2022-24787 CVE-2022-24787: Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine
Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. In version 0.3.1 and prior, bytestrings can have dirty bytes in them, resulting in the word-for-word comparisons giving incorrect results. Even without dirty nonzero bytes, two bytestrings can compare to equal if one ends with `"\x00"` because there is no comparison of the length. A patch is available and expected to be part of the 0.3.2 release. There are currently no known workarounds.
OSV
Incorrect Comparison in Vyper
osv·2022-04-04
CVE-2022-24787 [HIGH] Incorrect Comparison in Vyper
Incorrect Comparison in Vyper
### Impact
bytestrings can have dirty bytes in them, resulting in the word-for-word comparison to give incorrect results, e.g.
```vyper
b1: Bytes[32] = b"abcdef"
b1 = slice(b1, 0, 1)
b2: Bytes[32] = b"abcdef"
t: bool = b1 == b2 # incorrectly evaluates to True
```
even without dirty nonzero bytes, because there is no comparison of the length, two bytestrings can compare to equal if one ends with `"\x00"`.
```vyper
b1: Bytes[32] = b"abc\0"
b2: Bytes[32] = b"abc"
t: bool = b1 == b2 # incorrectly evaluates to True
```
### Patches
fixed in https://github.com/vyperlang/vyper/commit/2c73f8352635c0a433423a5b94740de1a118e508
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/vyperlang/vyper/commit/2c73f8352635c0a433423a5b94740de1a118e508https://github.com/vyperlang/vyper/security/advisories/GHSA-7vrm-3jc8-5wwmhttps://github.com/vyperlang/vyper/commit/2c73f8352635c0a433423a5b94740de1a118e508https://github.com/vyperlang/vyper/security/advisories/GHSA-7vrm-3jc8-5wwm
2022-04-04
Published