dbcve.org
Warnings Next GenerationApplication · Jenkins

CVE-2019-1003023

MEDIUM · 6.1 CVSS v3.0 Published 2019-02-06
Fix available
A fix is available. Upgrade to after 1.0.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A cross-site scripting vulnerability exists in Jenkins Warnings Next Generation Plugin 1.0.1 and earlier in src/main/java/io/jenkins/plugins/analysis/core/model/DetailsTableModel.java, src/main/java/io/jenkins/plugins/analysis/core/model/SourceDetail.java, src/main/java/io/jenkins/plugins/analysis/core/model/SourcePrinter.java, src/main/java/io/jenkins/plugins/analysis/core/util/Sanitizer.java, src/main/java/io/jenkins/plugins/analysis/warnings/DuplicateCodeScanner.java that allows attackers with the ability to control warnings parser input to have Jenkins render arbitrary HTML.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-site scripting (XSS) vulnerability in Jenkins Warnings Next Generation Plugin versions 1.0.1 and earlier. The vulnerability exists in multiple model and utility classes (DetailsTableModel.java, SourceDetail.java, SourcePrinter.java, Sanitizer.java, DuplicateCodeScanner.java) where warnings parser input is rendered without proper sanitization, allowing attackers to inject arbitrary HTML into Jenkins pages.

MitigationUpgrade Jenkins Warnings Next Generation Plugin to a version newer than 1.0.1, or implement proper HTML encoding/sanitization on all warning parser input paths before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Warnings Next GenerationApplication
Affected:<= 1.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Jenkins is installed
    Check if Jenkins is running by accessing the web UI or checking for the jenkins process (ps aux | grep jenkins)
    Affected if Jenkins is not present - the vulnerability does not apply
  2. Locate the Warnings Next Generation Plugin
    Navigate to Manage Jenkins > Manage Plugins > Installed, or check the filesystem at $JENKINS_HOME/plugins/ for a file named warnings-ng.jpi or warnings-next-generation.jpi
    Affected if The plugin file is not found - the vulnerability does not apply
  3. Check the plugin version
    In the Jenkins UI, find the Warnings Next Generation Plugin in the Installed tab and read the Version column, or inspect the plugin manifest: unzip -p $JENKINS_HOME/plugins/warnings-ng.jpi META-INF/MANIFEST.MF | grep Implementation-Version
    Affected if The version is 1.0.1 or earlier - the environment is potentially affected
  4. Verify the plugin is enabled
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and confirm the Warnings Next Generation Plugin status is 'Enabled', or check $JENKINS_HOME/plugins/warnings-ng.jpi.disabled does not exist
    Affected if The plugin is not enabled - the vulnerability cannot be exploited through this plugin
  5. Confirm plugin is in use
    Check Jenkins jobs for freestyle or pipeline jobs using the 'Warnings NG' or 'Record compiler warnings' build step, or look for warnings-ng-related configurations in job config.xml files under $JENKINS_HOME/jobs/
    Affected if No jobs use the plugin - the attack surface is not exposed even if the vulnerable version is installed

A user is affected if Jenkins runs with the Warnings Next Generation Plugin installed, enabled, version 1.0.1 or earlier, and actively used in at least one job configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 1.0.1
Interim mitigation

Upgrade Jenkins Warnings Next Generation Plugin to a version newer than 1.0.1, or implement proper HTML encoding/sanitization on all warning parser input paths before rendering.

Fix this in Warnings Next Generation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1003023 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1003023 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data