Log ParserApplication · Jenkins
CVE-2019-10410
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 · uneditedJenkins Log Parser Plugin 2.0 and earlier did not escape an error message, resulting in a cross-site scripting vulnerability exploitable by users able to define log parsing rules.
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 confidenceJenkins Log Parser Plugin 2.0 and earlier fails to escape an error message in the log parsing rule configuration, resulting in a stored cross-site scripting (XSS) vulnerability. Authenticated users with permissions to define log parsing rules can inject malicious JavaScript that executes in the browsers of other users viewing these rules.
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
Log ParserApplication
<= 2.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Log Parser Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Log Parser' or check the plugin directory $JENKINS_HOME/plugins for log-parser plugin folderAffected if The Log Parser plugin is not installed or no log parsing rules are configured, the vulnerability does not apply
-
Check installed plugin versionIn Manage Jenkins > Manage Plugins > Installed tab, find Log Parser Plugin and note the version columnAffected if Version is 2.0 or earlier (e.g., 2.0, 1.8, 1.7, etc.)
-
Identify configured log parsing rulesNavigate to Manage Jenkins > Configure System > Log Parser section, or check $JENKINS_HOME/config.xml for <logParser> entries, or look for files in $JENKINS_HOME/log-parser-rules/Affected if Any log parsing rules are defined in the Jenkins configuration
-
Check permissions on Log Parser RulesNavigate to Manage Jenkins > Manage and Assign Permissions and review which users or groups have the 'Log Parser Rules' permission (or appropriate permissions in the authorization matrix)Affected if Users other than trusted administrators have permissions to configure or edit log parsing rules
If the Log Parser Plugin version is 2.0 or earlier AND log parsing rules are configured AND untrusted users have permissions to edit those rules, the environment is vulnerable to CVE-2019-10410.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to Jenkins Log Parser Plugin version 2.1 or later which properly escapes error messages. If immediate patching is not feasible, restrict the 'Log Parser Rules' permission to only trusted administrators.
Fix this in Log Parser
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10410 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10410 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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