Skip to content

Use of unclaimed s3 bucket in tests and examples

Moderate severity GitHub Reviewed Published Nov 10, 2022 in deeplearning4j/deeplearning4j • Updated Jan 28, 2023

Package

maven org.deeplearning4j:dl4j-examples (Maven)

Affected versions

<= 1.0.0-M2.1

Patched versions

None
maven org.deeplearning4j:platform-tests (Maven)
<= 1.0.0-M2.1
None

Description

Impact

People who use some older NLP examples that reference the old S3 bucket.

Patches

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.

Workarounds

Download a word2vec google news vector from a new source using git lfs

References

@eclipsewebmaster eclipsewebmaster published to deeplearning4j/deeplearning4j Nov 10, 2022
Published by the National Vulnerability Database Nov 10, 2022
Published to the GitHub Advisory Database Nov 10, 2022
Reviewed Nov 10, 2022
Last updated Jan 28, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.079%
(36th percentile)

Weaknesses

CVE ID

CVE-2022-36022

GHSA ID

GHSA-rc39-g977-687w

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.