How many CVEs have patched _check_valid_range_constant?

1 published CVEs changed _check_valid_range_constant in vyperlang/vyper, in 1 distinct patches totalling 9 changed lines, between 2024 and 2024.

What is the latest CVE that changed _check_valid_range_constant?

CVE-2024-32481 (vyper's range(start, start + N) reverts for negative numbers), published 2024-04-25, changed lines 228 of vyper/codegen/stmt.py.

How does _check_valid_range_constant compare to the rest of vyperlang/vyper?

vyperlang/vyper has 30 CVEs with a located fix in total; 1 of them changed _check_valid_range_constant.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

vyperlang/vyper

Function

_check_valid_range_constant

Name: _check_valid_range_constant in vyperlang/vyper: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

vyper/codegen/stmt.py

Last patched April 25, 2024

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

9

Lines changed

Added plus removed

2024

Years

By CVE publication date

Overview

_check_valid_range_constant in vyperlang/vyper was changed by 1 published CVE fixes in 2024, in 1 distinct patches that added or removed 9 lines in total.

vyperlang/vyper has 30 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed _check_valid_range_constant, newest first, with the lines each fix touched.

vyper's range(start, start + N) reverts for negative numbers
CVE-2024-32481 · line 228 · +0 −9
Medium · CVSS 5.3
EPSS 0.8%2024-04-25

Get an alert when the next CVE fix lands in vyperlang/vyper, with the patched functions.

Monitor vyper CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in vyperlang/vyper changed by the most CVE fixes.

build_IR11 CVEs · vyper/builtins/functions.py from_FunctionDef4 CVEs · vyper/semantics/types/function.py generate_default_arg_sigs3 CVEs · vyper/ast/signatures/sig_utils.py extract_sigs3 CVEs · vyper/ast/signatures/interface.py _get_external_signatures3 CVEs · vyper/ast/signatures/interface.py mk_full_signature_from_json3 CVEs · vyper/ast/signatures/interface.py

All patched functions in vyperlang/vyper

Frequently asked questions

Common questions about CVE fixes to _check_valid_range_constant.

How many CVEs have patched _check_valid_range_constant?: 1 published CVEs changed _check_valid_range_constant in vyperlang/vyper, in 1 distinct patches totalling 9 changed lines, between 2024 and 2024.
What is the latest CVE that changed _check_valid_range_constant?: CVE-2024-32481 (vyper's range(start, start + N) reverts for negative numbers), published 2024-04-25, changed lines 228 of vyper/codegen/stmt.py.
How does _check_valid_range_constant compare to the rest of vyperlang/vyper?: vyperlang/vyper has 30 CVEs with a located fix in total; 1 of them changed _check_valid_range_constant.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track vyperlang/vyper CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing