Summary
Use of unclaimed s3 bucket in tests and examples
Workarounds
Download a word2vec google news vector from a new source using git lfs
Impact
People who use some older NLP examples that reference the old S3 bucket.
Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.
CVE-2022-36022 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The problem has been patched. Upgrade to snapshots for now. A release will be published later to address this due to the vulnerability mostly being examples and 1 class in the actual code base.
Frequently Asked Questions
- What is CVE-2022-36022? CVE-2022-36022 is a medium-severity use of insufficiently random values vulnerability in org.deeplearning4j:platform-tests (maven), affecting versions <= 1.0.0-M2.1. No fixed version is listed yet. Security-sensitive operations rely on values that are predictable or insufficiently random.
- How severe is CVE-2022-36022? CVE-2022-36022 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2022-36022?
org.deeplearning4j:platform-tests(maven) (versions <= 1.0.0-M2.1)org.deeplearning4j:dl4j-examples(maven) (versions <= 1.0.0-M2.1)
- Is there a fix for CVE-2022-36022? No fixed version is listed for CVE-2022-36022 yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is CVE-2022-36022 exploitable, and should I be worried? Whether CVE-2022-36022 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-36022 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-36022? No fixed version is listed yet. In the interim: Use a cryptographically secure random number generator (CSPRNG) for all security-sensitive values.