CVE-2023-32675
Vyper's nonpayable default functions are sometimes payable
Auswirkung
### Impact in contracts with at least one regular nonpayable function, due to the callvalue check being inside of the selector section, it is possible to send funds to the default function by using less than 4 bytes of calldata, even if the default function is marked `nonpayable`. this applies to contracts compiled with vyper<=0.3.7. ```vyper # @version 0.3.7 # implicitly nonpayable @external def foo() -> uint256: return 1 # implicitly nonpayable @external def __default__(): # could receive ether here pass ``` ### Patches this was fixed by the removal of the global calldatasize check in https://github.com/vyperlang/vyper/commit/02339dfda0f3caabad142060d511d10bfe93c520. ### Workarounds don't use nonpayable default functions
Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, ohne Anmeldung, ohne Zutun eines Nutzers. Dafür müssen bestimmte Bedingungen erfüllt sein, was einen Angriff erschwert. Bei Erfolg: geringes Risiko, dass Daten oder Systeme verändert werden.
Betroffene Pakete
| Ökosystem | Paket | Betroffen | Behoben in |
|---|---|---|---|
| pip | vyper | < 0.3.8 | 0.3.8 |
Betroffene Produkte · Vyperlang
| Produkt | Betroffene Versionen |
|---|---|
| Vyper | vor 0.3.8 |
Schwachstellenklasse
Referenzen
- NVD-Eintrag
- CVE.org-Eintrag
- GitHub-Advisory
- https://github.com/vyperlang/vyper/commit/02339dfda0f3caabad142060d511d10bfe93c520
- https://github.com/vyperlang/vyper/security/advisories/GHSA-vxmm-cwh2-q762
- https://github.com/advisories/GHSA-vxmm-cwh2-q762
- https://nvd.nist.gov/vuln/detail/CVE-2023-32675
- https://github.com/vyperlang/vyper/commit/903727006c1e5ebef99fa9fd5d51d62bd33d72a9
- https://github.com/pypa/advisory-database/tree/main/vulns/vyper/PYSEC-2023-80.yaml
- https://github.com/vyperlang/vyper/commit/02339dfda0f3caabad142060d511d10bfe93c520.