How severe is GHSA-r9jf-hf9x-7hrv?

GHSA-r9jf-hf9x-7hrv 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-r9jf-hf9x-7hrv?

GHSA-r9jf-hf9x-7hrv affects the following packages: org.jenkins-ci.plugins:script-security (Maven). Ecosystems affected: Maven.

How do I fix GHSA-r9jf-hf9x-7hrv?

Update org.jenkins-ci.plugins:script-security to 1.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r9jf-hf9x-7hrv is resolved across your whole dependency graph.

How do I detect GHSA-r9jf-hf9x-7hrv in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:script-security. 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-r9jf-hf9x-7hrv 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-r9jf-hf9x-7hrv?

O3 pinpoints whether GHSA-r9jf-hf9x-7hrv 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-r9jf-hf9x-7hrv actively exploited in the wild?

No public exploit code has been indexed for GHSA-r9jf-hf9x-7hrv 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-r9jf-hf9x-7hrv?

GHSA-r9jf-hf9x-7hrv is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-r9jf-hf9x-7hrv published, and has it been updated?

GHSA-r9jf-hf9x-7hrv was published on May 14, 2022 and was last updated on February 20, 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-r9jf-hf9x-7hrv

MEDIUM

GHSA-r9jf-hf9x-7hrv is a medium-severity (CVSS 6.5) Information Exposure vulnerability in org.jenkins-ci.plugins:script-security. O3 Security confirms whether GHSA-r9jf-hf9x-7hrv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Exposure of Sensitive Information to an Unauthorized Actor Jenkins Script Security Plugin

Also known asCVE-2017-1000505

Published

May 14, 2022

Updated

Feb 20, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:script-security

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

In Jenkins Script Security Plugin version 1.36 and earlier, users with the ability to configure sandboxed Groovy scripts are able to use a type coercion feature in Groovy to create new File objects from strings. This allowed reading arbitrary files on the Jenkins master file system. Such a type coercion is now subject to sandbox protection and considered to be a call to the new File(String) constructor for the purpose of in-process script approval.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:script-security`	all versions	1.37

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:script-security. 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:script-security to 1.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r9jf-hf9x-7hrv 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-r9jf-hf9x-7hrv 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-r9jf-hf9x-7hrv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Jenkins Script Security Plugin version 1.36 and earlier, users with the ability to configure sandboxed Groovy scripts are able to use a type coercion feature in Groovy to create new `File` objects from strings. This allowed reading arbitrary files on the Jenkins master file system. Such a type coercion is now subject to sandbox protection and considered to be a call to the `new File(String)` constructor for the purpose of in-process script approval.

O3 Security · Impact-Aware SCA

Is GHSA-r9jf-hf9x-7hrv in your dependencies?

O3 detects GHSA-r9jf-hf9x-7hrv 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