How severe is GHSA-pvjf-4hfg-wr84?

GHSA-pvjf-4hfg-wr84 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-pvjf-4hfg-wr84?

GHSA-pvjf-4hfg-wr84 affects the following packages: org.jenkins-ci.plugins:gradle (Maven). Ecosystems affected: Maven.

How do I fix GHSA-pvjf-4hfg-wr84?

Update org.jenkins-ci.plugins:gradle to 2.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pvjf-4hfg-wr84 is resolved across your whole dependency graph.

How do I detect GHSA-pvjf-4hfg-wr84 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:gradle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-pvjf-4hfg-wr84 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-pvjf-4hfg-wr84?

O3 pinpoints whether GHSA-pvjf-4hfg-wr84 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-pvjf-4hfg-wr84 actively exploited in the wild?

No public exploit code has been indexed for GHSA-pvjf-4hfg-wr84 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-pvjf-4hfg-wr84?

GHSA-pvjf-4hfg-wr84 is classified as CWE-670 (CWE-670). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-pvjf-4hfg-wr84 published, and has it been updated?

GHSA-pvjf-4hfg-wr84 was published on July 26, 2023 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-pvjf-4hfg-wr84

MEDIUM

GHSA-pvjf-4hfg-wr84 is a medium-severity (CVSS 6.5) CWE-670 vulnerability in org.jenkins-ci.plugins:gradle. O3 Security confirms whether GHSA-pvjf-4hfg-wr84 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Incorrect control flow in Jenkins Gradle Plugin breaks credentials masking in the build log

Also known asCVE-2023-39152

Published

Jul 26, 2023

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:gradle

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Always-incorrect control flow implementation in Jenkins Gradle Plugin 2.8 may result in credentials not being masked (i.e., replaced with asterisks) in the build log in some circumstances.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:gradle`	all versions	2.8.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:gradle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.jenkins-ci.plugins:gradle to 2.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pvjf-4hfg-wr84 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-pvjf-4hfg-wr84 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-pvjf-4hfg-wr84. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Always-incorrect control flow implementation in Jenkins Gradle Plugin 2.8 may result in credentials not being masked (i.e., replaced with asterisks) in the build log in some circumstances.

O3 Security · Impact-Aware SCA

Is GHSA-pvjf-4hfg-wr84 in your dependencies?

O3 detects GHSA-pvjf-4hfg-wr84 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works