VyperApplication · Vyperlang
CVE-2024-24559
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVyper is a Pythonic Smart Contract Language for the EVM. There is an error in the stack management when compiling the `IR` for `sha3_64`. Concretely, the `height` variable is miscalculated. The vulnerability can't be triggered without writing the `IR` by hand (that is, it cannot be triggered from regular vyper code). `sha3_64` is used for retrieval in mappings. No flow that would cache the `key` was found so the issue shouldn't be possible to trigger when compiling the compiler-generated `IR`. This issue isn't triggered during normal compilation of vyper code so the impact is low. At the time of publication there is no patch available.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceVyper compiler has a stack management error in IR compilation for sha3_64, where the height variable is miscalculated. The vulnerability affects mapping retrieval operations but can only be triggered by manually writing IR code, not from regular Vyper source code. No exploitation path was identified in normal compiler-generated IR flows.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
VyperApplication
<= 0.3.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Vyper compiler versionRun 'vyper --version' or 'python -c "import vyper; print(vyper.__version__)"' to determine the installed version numberAffected if The installed version is 0.3.10 or lower
-
Identify manually written IR code in the compilation pipelineReview your build process to determine if any manually crafted IR (Intermediate Representation) files (.ir or similar) are being passed to the Vyper compilerAffected if Manually written IR code is being compiled by Vyper
-
Inspect IR code for sha3_64 usageIf manually written IR is being compiled, search the IR source files for the 'sha3_64' operation or function callAffected if The manually written IR code contains sha3_64 operations
A user is affected only if they are manually compiling IR code that uses sha3_64, with Vyper version 0.3.10 or lower; regular Vyper source code compilation is not impacted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUntil a patch is released, ensure only trusted IR is compiled and avoid manually writing IR that uses sha3_64. Monitor Vyper security advisories for patch availability.
Vyper 0.3.11 or later (preferably latest stable release)
- 1. Identify the current Vyper compiler version in your project by checking your dependency files (e.g., requirements.txt, setup.py, or poetry.lock)
- 2. Upgrade Vyper to version 0.3.11 or later (preferably the latest stable release) using your package manager (e.g., pip install vyper==0.3.11 or pip install --upgrade vyper)
- 3. Verify the upgrade was successful by running: vyper --version
- 4. Rebuild and redeploy any smart contracts if needed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Vyper
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24559 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-24559 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data