CVE-2019-1003029

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Jenkins Script Security Plugin. For every flaw being used in attacks, see Exploited flaws; for Jenkins’s, see Jenkins flaws being used in attacks.

CVE-2019-1003029 is a security flaw in Jenkins Script Security Plugin. Attackers can run their own code on Jenkins Script Security Plugin. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 25 Apr 2022.[1]

Jenkins Script Security Plugin is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff.

Description

CISA calls it a sandbox bypass in Jenkins Script Security Plugin. In its words: “Jenkins Script Security Plugin contains a protection mechanism failure, allowing an attacker to bypass the sandbox.”[1]

The CVE record adds: “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.”[2]

It scores 9.9 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by NVD using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it. CISA names the product as Jenkins Script Security Plugin.

Most families won’t have Jenkins Script Security Plugin; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 25 Apr 2022, 1,144 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 16 May 2022 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 74%. That’s in the top 1% of the flaws it scores.[3]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

CISA’s required action: “Apply updates per vendor instructions.”[1]

  1. Check whether you use it.Jenkins Script Security Plugin is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 16 May 2022 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 9.9.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 74%.[3]

See also

Other Jenkins flaws

  • CVE-2017-1000353, Jenkins: remote code execution ·
  • CVE-2024-23897, Jenkins Command Line Interface (CLI): command line interface (CLI) path traversal ·
  • CVE-2015-5317, Jenkins User Interface (UI): user interface (UI) information disclosure ·
  • CVE-2019-1003030, Jenkins Matrix Project Plugin: remote code execution ·
  • CVE-2018-1000861, Jenkins Stapler Web Framework: stapler web framework deserialization of untrusted data ·

Similar flaws

  • CVE-2026-111357, Ivanti Connect Secure: missing authentication for critical function ·
  • CVE-2026-97229, GitLab Community Edition and Enterprise Edition: integer overflow or wraparound ·
  • CVE-2026-76418, Cisco Secure Firewall ASA Software and Cisco Secure FTD Software: unchecked return value to NULL pointer dereference ·
  • CVE-2026-48356, Adobe Commerce and Magento: unrestricted upload of file with dangerous type ·
  • CVE-2026-111497, Google Brotli: unchecked return value ·

Added the same day

  • CVE-2022-29464, WSO2 products: unrestrictive upload of file ·
  • CVE-2022-26904, Microsoft Windows: user profile service privilege escalation ·
  • CVE-2022-21919, Microsoft Windows: user profile service privilege escalation ·
  • CVE-2022-0847, Linux Kernel: privilege escalation ·
  • CVE-2021-41357, Microsoft Win32k: privilege escalation ·

Every Jenkins flaw on CISA’s list · Everything added in April 2022

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Jenkins Script Security Plugin Sandbox Bypass Vulnerability”. Known Exploited Vulnerabilities Catalog, added 25 Apr 2022.
  2. ^ National Institute of Standards and Technology. “CVE-2019-1003029 Detail”. National Vulnerability Database, published 8 Mar 2019.
  3. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.744, percentile 99.5, 31 Oct 2026.
  4. CVE Program. “CVE-2019-1003029”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.