LiveActive security incident?Get immediate response
CVE Record

CVE-2019-1003029: A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.53 and earlier in src/main/java/o...

A sandbox bypass vulnerability exists in Jenkins Script Security Plugin 1.53 and earlier in src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovySandbox.java, src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/SecureGroovyScript.java that allows attackers with Overall/Read permission to execute arbitrary code on the Jenkins master JVM.

CriticalCVSS 9.9Known exploitedUpdated
Discuss exposureBack to CVEs
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

This flaw lets a low-privileged Jenkins user bypass script sandbox protections and run arbitrary code on the Jenkins master JVM. For a build system, that can mean compromise of source code, build secrets, credentials, and deployment pipelines.

Executive priority

Treat as urgent for any Jenkins environment. A compromised controller can expose software supply chain secrets and deployment authority. Prioritize internet-facing, shared, or production Jenkins systems first.

Technical view

CVE-2019-1003029 affects Jenkins Script Security Plugin 1.53 and earlier. The vulnerable sandbox handling in GroovySandbox.java and SecureGroovyScript.java allows attackers with Overall/Read permission to execute arbitrary code on the Jenkins master JVM. CVSS is 9.9 critical.

Likely exposure

Exposure is most likely where Jenkins uses Script Security Plugin 1.53 or earlier and grants Overall/Read to untrusted, broad, or compromised accounts. Internet-facing or widely accessible Jenkins controllers are higher concern.

Exploitation context

CISA KEV marks this CVE as known exploited. The provided bundle does not include campaign details, exploitation volume, or evidence of current active targeting, so those specifics should not be assumed.

Researcher notes

Evidence identifies a sandbox bypass in Jenkins Script Security Plugin internals. The privilege requirement is low, Overall/Read, and impact is arbitrary code execution on the master JVM. KEV confirms known exploitation, but source detail is limited.

Mitigation direction

  • Inventory Jenkins Script Security Plugin versions across all controllers.
  • Apply Jenkins or distribution vendor updates for the Script Security Plugin.
  • Restrict Overall/Read to trusted users only.
  • Review Jenkins exposure and limit access to administrative networks.
  • Check Jenkins and distribution advisories for environment-specific guidance.

Validation and detection

  • Confirm no Jenkins controller runs Script Security Plugin 1.53 or earlier.
  • Review user and group assignments with Overall/Read permission.
  • Verify plugin update status through Jenkins administrative inventory.
  • Check for unexpected pipeline, script approval, or controller execution activity.
  • Confirm compensating access controls on exposed Jenkins instances.
Prepared
Reviewed
Confidence
high
Sources
5

Public sources used

Michael Williams reviewed this cited source version on .

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-1003029 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.9 (3.1)
Known Exploited
Yes
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.9Critical
CVSS 3.1 vector shape for CVE-2019-1003029Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Jenkins projectJenkins Script Security Plugin1.53 and earlierListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.