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 .. .
CVE-2022-31159
“—” beside the score: it is equal to NVD's CVSS score.
Score 7.9 from GitHub Security Advisory (severity: HIGH) published 2022-07-15. NVD baseline CVSS 7.9; sources differ by 0.0.
Also known asEUVD-2022-6311 (ENISA EUVD) · GHSA-c28r-hw5m-5gv3 (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 7.9
- EG Score
- 7.9HIGHmedium confidence
- EG Risk
- 52EG Risk 52/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity79% × 45%Impact severity (EG Severity): CVSS 7.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 1.6%
- EPSS %ILE
- 76th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.9): severity, escalated by confirmed exploitation. This CVE's 7.9 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.9 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 1.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
July 15, 2022
Last Modified
November 21, 2024
Advisory Details (1)
Auto-updated Sep 21, 2026Partial Path Traversal in com.amazonaws:aws-java-sdk-s3 · Advisory · aws/aws-sdk-java · GitHub
https://github.com/aws/aws-sdk-java/security/advisories/GHSA-c28r-hw5m-5gv3Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| maven | com.amazonaws:aws-java-sdk-s3 @ 1.12.261 (fixes < 1.12.261) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| com.amazonaws:aws-java-sdk-s3 | 1.10.0 ... 1.9.9 (1420 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 38× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 99 of 218 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 16:38 UTCEPSS rescoreEPSS 1.6% · 76th percentile
- 2026-11-01 16:30 UTCEPSS rescoreEPSS 1.6% · 76th percentile
- 2026-11-01 08:26 UTCGHSA enrichmentGHSA-c28r-hw5m-5gv3 · GitHub severity HIGH · GitHub CVSS 7.9
- 2026-11-01 08:26 UTCEG score recompute
- 2026-10-31 16:29 UTCEPSS rescoreEPSS 1.6% · 76th percentile
- 2026-10-30 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-29 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-28 16:28 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-27 21:47 UTCEG score recompute
- 2026-10-27 16:28 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-26 16:28 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-25 18:08 UTCEG score recompute
- 2026-10-25 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-24 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-21 16:28 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-21 07:20 UTCEG score recompute
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-18 08:35 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-16 16:34 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-16 09:24 UTCOSV refresh
Show 74 moreShow fewer
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-12 18:54 UTCEG score recompute
- 2026-10-12 16:30 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-11 23:19 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-05 17:40 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-03 14:23 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 1.6% · 75th percentile
- 2026-09-30 15:55 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-29 15:16 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-28 13:48 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-27 13:42 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-26 15:54 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-26 00:22 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-24 17:16 UTCOSV refresh
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-22 14:44 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-18 19:24 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-15 03:06 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-13 16:44 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-11 14:49 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 1.5% · 73rd percentile
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 1.4% · 71st percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 1.4% · 71st percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-09-05 09:14 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 1.4% · 71st percentile
- 2026-09-04 05:04 UTCEPSS rescoreEPSS 1.4% · 71st percentile
- 2026-09-02 14:09 UTCEPSS rescoreEPSS 1.4% · 71st percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 1.4% · 71st percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 1.4% · 71st percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-27 14:22 UTCEPSS rescoreEPSS 1.4% · 71st percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 1.4% · 71st percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 1.4% · 71st percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-23 00:16 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-20 22:52 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-18 19:37 UTCOSV refresh
- 2026-08-18 13:45 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-16 14:53 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-15 01:27 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-13 21:57 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-11 13:38 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-09 13:44 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-08 16:34 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-07 16:24 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-06 13:44 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-05 19:15 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-04 15:07 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-04 10:35 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-03 15:27 UTCOSV refresh
- 2026-08-03 10:33 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-02 02:24 UTCEPSS rescoreEPSS 1.4% · 70th percentile
- 2026-08-01 04:13 UTCEPSS rescoreEPSS 1.4% · 70th percentile
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2022-31159?
When was the CVE record for CVE-2022-31159 published?
Is CVE-2022-31159 actively exploited?
What is the CVSS score of CVE-2022-31159?
How do I remediate CVE-2022-31159?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-31159
Is Your Infrastructure Affected by CVE-2022-31159?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.