CVE-2024-55459
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 · uneditedAn issue in keras 3.7.0 allows attackers to write arbitrary files to the user's machine via downloading a crafted tar file through the get_file function.
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 · moderate confidenceKeras 3.7.0's get_file function is vulnerable to a path traversal attack when extracting downloaded tar archives. Attackers can craft malicious tar files containing paths with traversal sequences (e.g., ../../../') that, when extracted by get_file, allow writing files to arbitrary locations on the user's filesystem instead of the intended destination directory.
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= 3.7.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 Keras versionRun 'python -c "import keras; print(keras.__version__)"' or check your requirements.txt/environment for the keras versionAffected if Version is exactly 3.7.0
-
Identify get_file usage in codeSearch your codebase for calls to keras.utils.get_file or from keras.utils import get_fileAffected if Your code calls the get_file function to download and extract archives
-
Determine source trustworthinessReview all get_file calls to identify if they download from untrusted or user-controlled sources (URLs not from trusted domains)Affected if get_file is used with URLs from untrusted or external sources
-
Verify archive extraction occursCheck if the extracted files from get_file calls are being used - the vulnerability triggers during tar extractionAffected if Your get_file usage results in tar archive extraction (not other archive types)
You are affected if you have Keras 3.7.0 installed AND use get_file to download/extract tar archives from untrusted sources.
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 · scopedUpgrade to a patched version of Keras when available. Until then, avoid using get_file with untrusted tar sources, validate all extracted paths, and consider implementing additional checks on downloaded archives before extraction.
Keras 3.8.0 or later (check PyPI for latest stable release)
- 1. Ensure you have a backup of your current project and any important data.
- 2. Upgrade Keras to the latest available version using pip: pip install --upgrade keras
- 3. Verify the upgrade was successful by checking the installed version: python -c "import keras; print(keras.__version__)"
- 4. Test your existing code that uses the get_file function to ensure compatibility with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55459 — 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-55459 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