CVE-2022-36022 — platform-tests
MEDIUMCVE-2022-36022 is a medium-severity (CVSS 5.3) CWE-344 vulnerability in org.deeplearning4j:platform-tests. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Some Deeplearning4J packages use unclaimed s3 bucket in tests and examples
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.deeplearning4j:platform-tests☕org.deeplearning4j:dl4j-examplesReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.deeplearning4j:platform-tests | all versions | No fix |
| ☕Maven | org.deeplearning4j:dl4j-examples | all versions | No fix |
Affected Products
deeplearning4jeclipseDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.deeplearning4j:platform-tests, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.deeplearning4j:platform-tests for CVE-2022-36022. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-36022 in your dependencies?
Find it across Maven, including transitive dependencies.