vyper
Affected
- introduced
0, fixed0.3.2(ecosystem)
Fixed versions
0.3.2
Fix
- Fixed version
0.3.2pip install --upgrade vyper==0.3.2
Advisory
Also known as: CVE-2022-24787, PYSEC-2022-196
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.
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".
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
High Basis: The source's own band: HIGH
0, fixed 0.3.2 (ecosystem)0.3.2
0.3.2pip install --upgrade vyper==0.3.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0