Security readout for executives and security teams
This is a critical Jenkins issue where someone who can control Pipeline scripts could escape the Groovy sandbox and run code on the Jenkins controller JVM. That can put build secrets, source access, deployment credentials, and CI/CD availability at risk. Exposure is most likely on Jenkins controllers running Pipeline: Groovy Plugin 2.63 or earlier, especially where less-trusted users, repositories, or automation can define or modify Pipeline scripts. Jenkins systems holding deployment credentials or production release permissions have higher business impact. Prioritize remediation immediately for production or shared Jenkins controllers. This vulnerability can turn limited Pipeline control into controller-level code execution, directly affecting software delivery integrity and secrets. KEV status makes delay difficult to justify. Mitigation focus: Update Pipeline: Groovy Plugin to a vendor-supported release newer than 2.63 after reviewing Jenkins guidance.; Apply Red Hat fixes where Jenkins is supplied through Red Hat packaging.; Restrict who can create, edit, or source Pipeline scripts until remediation is complete..
Michael Williams reviewed this cited source version on .
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.
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution 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 lookupCVE-2019-1003030 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CISA KEV status
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.9CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://jenkins.io/security/advisory/2019-03-06/#SECURITY-1336%20%282%29CVE reference · x_refsource_CONFIRM
- RHSA-2019:0739CVE reference · vendor-advisory, x_refsource_REDHAT
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2019-1003030CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.