Vulnerability in vyper (CVE-2023-41052)
Summary
Vulnerability in vyper (CVE-2023-41052). Risk of unauthorized operations or information disclosure. Exploitable via uint256_addmod. Mitigation: upgrade to 0.3.10 or later.
Original description
The description as published by the source.
Impact
The order of evaluation of the arguments of the builtin functions uint256_addmod, uint256_mulmod, ecadd and ecmul does not follow source order.
• For uint256_addmod(a,b,c) and uint256_mulmod(a,b,c), the order is c,a,b.
• For ecadd(a,b) and ecmul(a,b), the order is b,a.
Note that this behaviour is problematic when the evaluation of one of the arguments produces side effects that other arguments depend on.
Patches
https://github.com/vyperlang/vyper/pull/3583
Workarounds
When using builtins from the list above, make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-41052 has been found in vyper.
Attackers can target a specific entry point like uint256_addmod over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade vyper to 0.3.10 or later.
If unsure, ask your IT team or search "vyper CVE-2023-41052" on the vendor's site.
CVE-2023-41052 (vyper) — CWE-670
Attack surface: uint256_addmod / uint256_mulmod / ecadd / ecmul
Patched: 0.3.10 — apply immediately
Workaround: When using builtins from the list above, make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-670) exists in vyper. Attackers reach the vulnerable code path via uint256_addmod.
Check the vendor advisory for the affected versions of vyper. Attack surface: uint256_addmod / uint256_mulmod / ecadd / ecmul.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.3.10.
Workaround: When using builtins from the list above, make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'vyper' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'vyper' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
vyperを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
When using builtins from the list above, make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects.パッチが適用されるまでの応急処置として、When using builtins from the list above, make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade vyper to 0.3.10ステージング環境で 0.3.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com