NVD / CVE Program· CNA GitHub_M

CVE-2023-35946: Dependency cache path traversal in Gradle

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: gradle (openSUSE:Leap 15.5) 4.4.1-150200.3.24.1; gradle (SUSE:Linux Enterprise Module for Development Tools 15 SP5) 4.4.1-150200.3.24.1.

Low priority for now. Upgrade to gradle (openSUSE:Leap 15.5) 4.4.1-150200.3.24.1; gradle (SUSE:Linux Enterprise Module for Development Tools 15 SP5) 4.4.1-150200.3.24.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Gradle is a build tool with a focus on build automation and support for multi-language development. When Gradle writes a dependency into its dependency cache, it uses the dependency's coordinates to compute a file location. With specially crafted dependency coordinates, Gradle can be made to write files into an unintended location. The file may be written outside the dependency cache or over another file in the dependency cache. This vulnerability could be used to poison the dependency cache or overwrite important files elsewhere on the filesystem where the Gradle process has write permissions. Exploiting this vulnerability requires an attacker to have control over a dependency repository used by the Gradle build or have the ability to modify the build's configuration. It is unlikely that this would go unnoticed. A fix has been released in Gradle 7.6.2 and 8.2 to protect against this vulnerability. Gradle will refuse to cache dependencies that have path traversal elements in their dependency coordinates. It is recommended that users upgrade to a patched version. If you are unable to upgrade to Gradle 7.6.2 or 8.2, `dependency verification` will make this vulnerability more difficult to exploit.

MediumCVSS 5.5 · v3.1—No exploit Fix available

Path traversal

SUSE-SU-2024:3163-1

Published: Jun 30, 2023
Updated: Oct 8, 2026
EPSS: 0.2% · 20th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 5.5
CNA · GitHub_M: 6.9; 1.4 point gap

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
gradle	gradle	cpe:2.3:a:gradle:gradle

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

gradle gradlebefore 7.6.2
gradle gradle8.0.0 and later · before 8.2.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

gradle gradle
- < 7.6.2, >= 8.0, < 8.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	gradle	from 0	—
openSUSE:Leap 15.5	gradle	before 4.4.1-150200.3.24.1	4.4.1-150200.3.24.1
SUSE:Linux Enterprise Module for Development Tools 15 SP5	gradle	before 4.4.1-150200.3.24.1	4.4.1-150200.3.24.1

Same product

gradle: all records

Other highest-scoring records for the same primary product.

CVE-2019-15052The HTTP client in Gradle before 5.6 sends authentication credentials originally destined for the configured host.
40Plan
CVE-2016-6199ObjectSocketWrapper.java in Gradle 2.12 allows remote attackers to execute arbitrary code via a crafted serialized object.
40Plan
CVE-2023-26053Gradle usage of long IDs for PGP keys opens potential for collision attacks
39Monitor

Published before and after this one in the same product

← EarlierCVE-2022-31156Jul 14, 2022 · Gradle's dependency verification can ignore checksum verification when signature verification cannot be performed
17Monitor
← EarlierCVE-2023-35947Jun 30, 2023 · Path traversal vulnerabilities in handling of Tar archives in Gradle
32Monitor
Later →CVE-2023-44387Oct 5, 2023 · Gradle has incorrect permission assignment for symlinked files used in copy or archiving operations
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
opensuse:gradle	4.4.1-150200.3.24.1 · openSUSE:Leap 15.5	Package registry (OSV)
suse:gradle	4.4.1-150200.3.24.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP5	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

SSVC exploitation— → noneOct 8, 2026, 11:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:48 PM UTC

For records you follow, these changes also arrive as notifications. →

References

docs.gradle.org/current/userguide/dependency_verification.html

Show all references (4 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records