First published: Mon Apr 04 2022(Updated: )
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.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Vyperlang Vyper | <=0.3.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-24787 is a vulnerability in the Vyper smart contract language that allows for incorrect word-for-word comparisons of bytestrings, resulting in incorrect results.
CVE-2022-24787 has a severity rating of 7.5 (high).
CVE-2022-24787 affects Vyperlang Vyper version 0.3.1 and prior, allowing for incorrect comparison of bytestrings.
To fix CVE-2022-24787, update to a version of Vyperlang Vyper that is 0.3.2 or later.
You can find more information about CVE-2022-24787 in the GitHub commit and advisory links: - GitHub Commit: [link] - GitHub Advisory: [link]