Skip to content

GHSA-r9jf-hf9x-7hrv CVE-2017-1000505

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

Medium Maven
Severity
6.5 / 10
Medium · CVSS 3.0
Exploit chance (EPSS)
0.99%
Chance of exploitation in the next 30 days. Higher than 62.64% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
Fix
1.37
Upgrade org.jenkins-ci.plugins:script-security to this version or later

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 versions

Maven

PackageVulnerableFixed in
org.jenkins-ci.plugins:script-security
< 1.37
1.37

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.jenkins-ci.plugins:script-security Maven → 1.37

maven
<dependency><groupId>org.jenkins-ci.plugins</groupId><artifactId>script-security</artifactId><version>1.37</version></dependency>
gradle
implementation("org.jenkins-ci.plugins:script-security:1.37")

Severity breakdown

CVSS 3.0 6.5

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

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2019-1003029
Sandbox bypass in Script Security Plugin
Critical Known exploited Also affects org.jenkins-ci.plugins:script-security
GHSA-cfj9-2vgr-hpxp
Jenkins Script Security Plugin has a script security bypass vulnerability
High Also affects org.jenkins-ci.plugins:script-security
GHSA-c3jm-9vj7-5v66
Jenkins Script Security Plugin sandbox bypass vulnerability
High Also affects org.jenkins-ci.plugins:script-security
GHSA-p334-gfhq-c7w6
Jenkins Script Security Plugin: Missing permission checks allow enumeration of pending and approved classpaths
Medium Also affects org.jenkins-ci.plugins:script-security
GHSA-jv82-75fh-23r7
Missing permission check in Jenkins Script Security Plugin
Medium Also affects org.jenkins-ci.plugins:script-security
GHSA-2g4q-9vm9-9fw4
Jenkins Script Security Plugin sandbox bypass vulnerability
High Also affects org.jenkins-ci.plugins:script-security
GHSA-v63g-v339-2673
Jenkins Script Security Plugin has sandbox bypass vulnerability involving crafted constructor bodies
Critical Also affects org.jenkins-ci.plugins:script-security
GHSA-76qj-9gwh-pvv3
Sandbox bypass in Jenkins Script Security Plugin
High Also affects org.jenkins-ci.plugins:script-security
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor