dbcve.org
Deeplearning4jApplication · Eclipse

CVE-2022-36022

MEDIUM · 5.3 CVSS v3.1 Published 2022-11-10
Fix available
A fix is available. Upgrade to 1.0.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Deeplearning4J is a suite of tools for deploying and training deep learning models using the JVM. Packages org.deeplearning4j:dl4j-examples and org.deeplearning4j:platform-tests through version 1.0.0-M2.1 may use some unclaimed S3 buckets in tests in examples. This is likely affect people who use some older NLP examples that reference an old S3 bucket. The problem has been patched. Users should upgrade to snapshots as Deeplearning4J plan to publish a release with the fix at a later date. As a workaround, download a word2vec google news vector from a new source using git lfs from here.

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 confidence

Deeplearning4J examples and platform tests (versions up to 1.0.0-M2.1) reference unclaimed S3 buckets for NLP word2vec Google News vector data. This creates a supply chain integrity risk where external data dependencies may be unavailable or potentially compromised by third parties who have claimed those bucket names.

MitigationUpgrade to snapshot versions when available, or manually download word2vec Google News vectors from the new git lfs source specified in the workaround. Remove or avoid running older NLP example code that depends on the deprecated S3 bucket references.

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
Deeplearning4jApplication
Affected:< 1.0.0= 1.0.0

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Deeplearning4j version in use
    Check the project's dependency management file (pom.xml for Maven, build.gradle for Gradle) or the library jar manifest for the Eclipse Deeplearning4j version
    Affected if The version is 1.0.0 or any version below 1.0.0 (such as 1.0.0-M2.1 or earlier)
  2. Locate S3 bucket URL references in source code
    Search the codebase for S3 URL patterns commonly used for word2vec data, typically strings containing 's3.amazonaws.com' and 'word2vec' or 'GoogleNews'
    Affected if The codebase contains references to deprecated S3 bucket URLs for NLP word2vec Google News vectors
  3. Identify NLP word2vec example or test code
    Search for imports and usages of org.deeplearning4j.examples.nlp.word2vec, or classes that load Google News vector files
    Affected if The project runs or depends on NLP examples or tests that download/use the Google News word2vec dataset
  4. Check runtime network connections to S3
    Monitor network traffic or review application logs during startup for attempts to connect to s3.amazonaws.com endpoints related to word2vec data
    Affected if The application attempts to fetch data from unclaimed S3 buckets at runtime

A user is affected if they are using Deeplearning4j version 1.0.0 or earlier and running NLP word2vec example code or tests that reference the deprecated S3 bucket for Google News vectors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.0.0 or later
Fixed in 1.0.0
Interim mitigation

Upgrade to snapshot versions when available, or manually download word2vec Google News vectors from the new git lfs source specified in the workaround. Remove or avoid running older NLP example code that depends on the deprecated S3 bucket references.

Recommended fix Moderate confidence

Latest Deeplearning4j snapshot (post-fix)

  1. 1. Update your Deeplearning4j dependency to use the latest snapshot version that includes the fix
  2. 2. For Maven projects, add or update the snapshot repository in your pom.xml: <repository><id>sonatype-oss-snapshots</id><url>https://oss.sonatype.org/content/repositories/snapshots</url></repository>
  3. 3. Update the dl4j-examples dependency version to the latest snapshot
  4. 4. If using NLP examples that reference word2vec Google News vectors, download the vector file from the new git lfs source referenced in the Deeplearning4j repository
  5. 5. Verify your application compiles and runs with the updated dependencies
Caveat Snapshots may contain other changes; thoroughly test your application after upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Deeplearning4j Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-36022 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-36022 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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