BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2022
CVE-2022-31159High confidence

Partial Path Traversal in com.amazonaws:aws-java-sdk-s3

aws · aws-sdk-java

Official source article: GitHub GHSA-C28R-HW5M-5GV3 ↗. Check the applicable product and release in the original source.

7.9HighCVSS 3.1
Recommended action
Within 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 22 Apr 2025

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • EPSS is 1.62% for the current model date.

Compensating controls

  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs aws aws-sdk-java and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2022-6311

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Fix not verified
01

What, why and how

The AWS SDK for Java enables Java developers to work with Amazon Web Services. A partial-path traversal issue exists within the `downloadDirectory` method in the AWS S3 TransferManager component of the AWS SDK for Java v1 prior to version 1.12.261. Applications using the SDK control the `destinationDirectory` argument, but S3 object keys are determined by the application that uploaded the objects. The `downloadDirectory` method allows the caller to pass a filesystem object in the object key but contained an issue in the validation logic for the key name. A knowledgeable actor could bypass the validation logic by including a UNIX double-dot in the bucket key. Under certain conditions, this could permit them to retrieve a directory from their S3 bucket that is one level up in the filesystem from their working directory. This issue’s scope is limited to directories whose name prefix matches the destinationDirectory. E.g. for destination directory`/tmp/foo`, the actor can cause a download to `/tmp/foo-bar`, but not `/tmp/bar`. If `com.amazonaws.services.s3.transfer.TransferManager::downloadDirectory` is used to download an untrusted buckets contents, the contents of that bucket can be written outside of the intended destination directory. Version 1.12.261 contains a patch for this issue. As a workaround, when calling `com.amazonaws.services.s3.transfer.TransferManager::downloadDirectory`, pass a `KeyFilter` that forbids `S3ObjectSummary` objects that `getKey` method return a string containing the substring `..` .

What

The AWS SDK for Java enables Java developers to work with Amazon Web Services. A partial-path traversal issue exists within the `downloadDirectory` method in the AWS S3 TransferManager component of the AWS SDK for Java v1 prior to version 1.12.261. Applications using the SDK control the `destinationDirectory` argument, but S3 object keys are determined by the application that uploaded the objects. The `downloadDirectory` method allows the caller to pass a filesystem object in the object key but contained an issue in the validation logic for the key name. A knowledgeable actor could bypass the validation logic by including a UNIX double-dot in the bucket key. Under certain conditions, this could permit them to retrieve a directory from their S3 bucket that is one level up in the filesystem from their working directory. This issue’s scope is limited to directories whose name prefix matches the destinationDirectory. E.g. for destination directory`/tmp/foo`, the actor can cause a download to `/tmp/foo-bar`, but not `/tmp/bar`. If `com.amazonaws.services.s3.transfer.TransferManager::downloadDirectory` is used to download an untrusted buckets contents, the contents of that bucket can be written outside of the intended destination directory. Version 1.12.261 contains a patch for this issue. As a workaround, when calling `com.amazonaws.services.s3.transfer.TransferManager::downloadDirectory`, pass a `KeyFilter` that forbids `S3ObjectSummary` objects that `getKey` method return a string containing the substring `..` .

Why

Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

The AWS SDK for Java enables Java developers to work with Amazon Web Services. A partial-path traversal issue exists within the `downloadDirectory` method in the AWS S3 TransferManager component of the AWS SDK for Java v1 prior to version 1.12.261. Applications using the SDK control the `destinationDirectory` argument, but S3 object keys are determined by the application that uploaded the objects. The `downloadDirectory` method allows the caller to pass a filesystem object in the object key but contained an issue in the validation logic for the key name. A knowledgeable actor could bypass the validation logic by including a UNIX double-dot in the bucket key. Under certain conditions, this could permit them to retrieve a directory from their S3 bucket that is one level up in the filesystem from their working directory. This issue’s scope is limited to directories whose name prefix matches the destinationDirectory. E.g. for destination directory`/tmp/foo`, the actor can cause a download to `/tmp/foo-bar`, but not `/tmp/bar`. If `com.amazonaws.services.s3.transfer.TransferManager::downloadDirectory` is used to download an untrusted buckets contents, the contents of that bucket can be written outside of the intended destination directory. Version 1.12.261 contains a patch for this issue. As a workaround, when calling `com.amazonaws.services.s3.transfer.TransferManager::downloadDirectory`, pass a `KeyFilter` that forbids `S3ObjectSummary` objects that `getKey` method return a string containing the substring `..` .

Why

Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
Required interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-22 ↗

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRLowPrivileges required: The attacker needs basic user-level privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-22Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-3663Atlassian Bamboo: Mehrere Schwachstellen

Ein entfernter Angreifer kann mehrere Schwachstellen in Atlassian Bamboo ausnutzen, um Dateien zu manipulieren oder einen Denial-of-Service-Zustand zu erzeugen.

Official advisory ↗
BSI · German · WID-SEC-2024-0794Dell ECS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell ECS ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode mit Administratorrechten auszuführen, Informationen offenzulegen, Dateien zu manipulieren, einen Cross-Site-Scripting-Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-0578IBM Security Guardium: Mehrere Schwachstellen

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in IBM Security Guardium ausnutzen, um Dateien zu manipulieren, beliebigen Programmcode auszuführen oder Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20220720Security Bulletin 20 Jul 2022

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 20 Jul 2022, published on 20 July 2022. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2021-47582 Référence CVE CVE-2021-47609 https://www.cve.org/CVERecord?id=CVE-2021-47609 Référence CVE CVE-2021-47624 https://www.cve.org/CVERecord?id=CVE-2021-47624 Référence CVE CVE-2022-2047 https://www.cve.org/CVERecord?id=CVE-2022-2047 Référence CVE CVE-2022-24785 https://www.cve.org/CVERecord?id=CVE-2022-24785 Référence CVE CVE-2022-24823 https://www.cve.org/CVERecord?id=CVE-2022-24823 Référence CVE CVE-2022-25168 https://www.cve.org/CVERecord?id=CVE-2022-25168 Référence CVE CVE-2022-25647 https://www.cve.org/CVERecord?id=CVE-2022-25647 Référence CVE CVE-2022-26612 https://www.cve.org/CVERecord?id=CVE-2022-26612 Référence CVE CVE-2022-31159 https://www.cve.org/CVERecord?id=CVE-2022-31159 Référence CVE CVE-2022-31160 https://www.cve.org/CVERecord?id=CVE-2022-31160 Référence CVE CVE-2022-3171 https://www.cve.org/CVERecord?id=CVE-2022-3171 Référence CVE CVE-2022-31777 https://www.cve.org/CVERecord?id=CVE-2022-31777 Référence CVE CVE-2022-33891 https://www.cve.org/CVERecord?id=CVE-2022-33891 Référence CVE CVE-2022-34169 https://www.cve.org/CVERecord?id=CVE-2022-34169 Référence CVE CVE-2022-3509 https://www.cve.org/CVERecord?id=CVE-2022-3509 Référence CVE CVE-2022-3510 https://www.cve.org/CVERecord?id=CVE-2022-3510 Référence CVE CVE-2022-36364 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0556Multiples vulnérabilités dans les produits VMware

rd?id=CVE-2022-1471 Référence CVE CVE-2022-24613 https://www.cve.org/CVERecord?id=CVE-2022-24613 Référence CVE CVE-2022-24614 https://www.cve.org/CVERecord?id=CVE-2022-24614 Référence CVE CVE-2022-25168 https://www.cve.org/CVERecord?id=CVE-2022-25168 Référence CVE CVE-2022-25857 https://www.cve.org/CVERecord?id=CVE-2022-25857 Référence CVE CVE-2022-26336 https://www.cve.org/CVERecord?id=CVE-2022-26336 Référence CVE CVE-2022-26612 https://www.cve.org/CVERecord?id=CVE-2022-26612 Référence CVE CVE-2022-30126 https://www.cve.org/CVERecord?id=CVE-2022-30126 Référence CVE CVE-2022-30973 https://www.cve.org/CVERecord?id=CVE-2022-30973 Référence CVE CVE-2022-31159 https://www.cve.org/CVERecord?id=CVE-2022-31159 Référence CVE CVE-2022-3171 https://www.cve.org/CVERecord?id=CVE-2022-3171 Référence CVE CVE-2022-32287 https://www.cve.org/CVERecord?id=CVE-2022-32287 Référence CVE CVE-2022-3509 https://www.cve.org/CVERecord?id=CVE-2022-3509 Référence CVE CVE-2022-3510 https://www.cve.org/CVERecord?id=CVE-2022-3510 Référence CVE CVE-2022-36364 https://www.cve.org/CVERecord?id=CVE-2022-36364 Référence CVE CVE-2022-38749 https://www.cve.org/CVERecord?id=CVE-2022-38749 Référence CVE CVE-2022-38750 https://www.cve.org/CVERecord?id=CVE-2022-38750 Référence CVE CVE-2022-38751 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0281Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2020-36518 Référence CVE CVE-2021-33910 https://www.cve.org/CVERecord?id=CVE-2021-33910 Référence CVE CVE-2021-35937 https://www.cve.org/CVERecord?id=CVE-2021-35937 Référence CVE CVE-2021-35938 https://www.cve.org/CVERecord?id=CVE-2021-35938 Référence CVE CVE-2021-35939 https://www.cve.org/CVERecord?id=CVE-2021-35939 Référence CVE CVE-2021-46877 https://www.cve.org/CVERecord?id=CVE-2021-46877 Référence CVE CVE-2022-23302 https://www.cve.org/CVERecord?id=CVE-2022-23302 Référence CVE CVE-2022-23305 https://www.cve.org/CVERecord?id=CVE-2022-23305 Référence CVE CVE-2022-23307 https://www.cve.org/CVERecord?id=CVE-2022-23307 Référence CVE CVE-2022-31159 https://www.cve.org/CVERecord?id=CVE-2022-31159 Référence CVE CVE-2022-3821 https://www.cve.org/CVERecord?id=CVE-2022-3821 Référence CVE CVE-2022-42003 https://www.cve.org/CVERecord?id=CVE-2022-42003 Référence CVE CVE-2022-42004 https://www.cve.org/CVERecord?id=CVE-2022-42004 Référence CVE CVE-2023-26118 https://www.cve.org/CVERecord?id=CVE-2023-26118 Référence CVE CVE-2023-26464 https://www.cve.org/CVERecord?id=CVE-2023-26464 Référence CVE CVE-2023-26604 https://www.cve.org/CVERecord?id=CVE-2023-26604 Référence CVE CVE-2023-33201 https://www.cve.org/CVERecord?id=CVE-2023-33201 Référence CVE CVE-2023-33202 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0473Multiples vulnérabilités dans les produits Splunk

De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données, une injection de code indirecte à distance (XSS) et un contournement de la politique de sécurité.

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0116Multiples vulnérabilités dans les produits IBM

VERecord?id=CVE-2020-4338 Référence CVE CVE-2020-4375 https://www.cve.org/CVERecord?id=CVE-2020-4375 Référence CVE CVE-2020-4465 https://www.cve.org/CVERecord?id=CVE-2020-4465 Référence CVE CVE-2020-4682 https://www.cve.org/CVERecord?id=CVE-2020-4682 Référence CVE CVE-2021-29843 https://www.cve.org/CVERecord?id=CVE-2021-29843 Référence CVE CVE-2021-38875 https://www.cve.org/CVERecord?id=CVE-2021-38875 Référence CVE CVE-2021-38949 https://www.cve.org/CVERecord?id=CVE-2021-38949 Référence CVE CVE-2022-21626 https://www.cve.org/CVERecord?id=CVE-2022-21626 Référence CVE CVE-2022-22970 https://www.cve.org/CVERecord?id=CVE-2022-22970 Référence CVE CVE-2022-31159 https://www.cve.org/CVERecord?id=CVE-2022-31159 Référence CVE CVE-2022-31772 https://www.cve.org/CVERecord?id=CVE-2022-31772 Référence CVE CVE-2022-34165 https://www.cve.org/CVERecord?id=CVE-2022-34165 Référence CVE CVE-2022-40231 https://www.cve.org/CVERecord?id=CVE-2022-40231 Référence CVE CVE-2022-40232 https://www.cve.org/CVERecord?id=CVE-2022-40232 Référence CVE CVE-2022-42003 https://www.cve.org/CVERecord?id=CVE-2022-42003 Référence CVE CVE-2022-42004 https://www.cve.org/CVERecord?id=CVE-2022-42004 Référence CVE CVE-2022-43579 https://www.cve.org/CVERecord?id=CVE-2022-43579 Référence CVE CVE-2023-23477 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2022-013383Amazon.com, Inc. の aws-sdk-java におけるパストラバーサルの脆弱性

Amazon.com, Inc. の aws-sdk-java には、パストラバーサルの脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix not verified
Affected
aws-sdk-java: <= 1.12.260
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 15 Jul 2022 · Last source change 22 Apr 2025, 17:49 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2022-6311
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2022-31159 · cve.blacktree.nl