CVE-2024-37902
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 · uneditedDeepJavaLibrary(DJL) is an Engine-Agnostic Deep Learning Framework in Java. DJL versions 0.1.0 through 0.27.0 do not prevent absolute path archived artifacts from inserting archived files directly into the system, overwriting system files. This is fixed in DJL 0.28.0 and patched in DJL Large Model Inference containers version 0.27.0. Users are advised to upgrade.
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 confidenceDJL versions 0.1.0 through 0.27.0 lack validation when extracting archived model artifacts, allowing files with absolute paths to be written directly to the filesystem during extraction. This path traversal vulnerability enables attackers to overwrite system files by crafting malicious archive files containing entries with absolute paths like /etc/passwd or other critical system locations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
-
Identify DJL version in your environmentSearch for DJL JAR files (djl-*.jar) in your application directories, check pom.xml or build.gradle dependencies, or run: find . -name 'djl*.jar' -exec jar manifest {} \; 2>/dev/null | grep -i versionAffected if The detected version is 0.1.0 through 0.27.0 (inclusive)
-
Locate DJL JAR files and manifestRun: find / -path '*/djl/*' -name '*.jar' 2>/dev/null | xargs -I {} sh -c 'unzip -p {} META-INF/MANIFEST.MF 2>/dev/null | grep -i implementation-version'Affected if DJL JAR files present with versions between 0.1.0 and 0.27.0
-
Determine if model artifact loading is usedReview application code for ModelZoo.loadModel(), TorchScriptModel, or other DJL model loading API calls; check for .zip, .tar.gz, or .jar model artifact files in your model directoriesAffected if Application loads model artifacts from archives using DJL versions 0.1.0-0.27.0
-
Audit filesystem for files extracted to suspicious locationsSearch for unexpected files in system directories: find /etc /var /usr -newer /path/to/djl.jar -type f 2>/dev/null | head -20Affected if Files exist in system directories (/etc, /var, /usr) that were created after or alongside DJL model extraction operations
You are affected if DJL version 0.1.0 through 0.27.0 is installed AND your application loads model artifacts from archive files, as this enables path traversal during extraction.
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 DJL to version 0.28.0 or later, or use DJL Large Model Inference containers version 0.27.0 or later to patch the path traversal vulnerability.
DJL 0.28.0
- Upgrade DeepJavaLibrary (DJL) to version 0.28.0 or later to resolve the path traversal vulnerability
- If using DJL Large Model Inference containers, ensure you are using version 0.27.0 or later which includes the patch
- Verify the upgrade by checking that archived artifacts with absolute paths can no longer write files outside the intended directory
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37902 — 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-37902 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