Defined in 2 files
Last patched
parse_Call in vyperlang/vyper was changed by 3 published CVE fixes between 2021 and 2024, in 3 distinct patches that added or removed 93 lines in total.
The name occurs in 2 files: vyper/old_codegen/stmt.py, vyper/old_codegen/expr.py.
vyperlang/vyper has 30 CVEs with a located fix in total, so 10% of them touched this function.
Every published CVE whose fix changed parse_Call, newest first, with the lines each fix touched.
CVE-2024-32648 · vyper/old_codegen/expr.py · lines 971–988 · +10 −16
CVE-2024-32648 · vyper/old_codegen/stmt.py · lines 139–143 · +3 −2
CVE-2021-41121 · vyper/old_codegen/expr.py · lines 971–988 · +10 −16
CVE-2021-41121 · vyper/old_codegen/stmt.py · lines 139–143 · +3 −2
CVE-2021-41122 · vyper/old_codegen/expr.py · lines 971–988 · +10 −16
CVE-2021-41122 · vyper/old_codegen/stmt.py · lines 139–143 · +3 −2
Get an alert when the next CVE fix lands in vyperlang/vyper, with the patched functions.
Monitor vyper CVEsFunctions in the same files that CVE fixes also changed.
Functions in vyperlang/vyper changed by the most CVE fixes.
Common questions about CVE fixes to parse_Call.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
