Flaky Test HandlerApplication · Jenkins
CVE-2023-40342
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 Flaky Test Handler Plugin 1.2.2 and earlier does not escape JUnit test contents when showing them on the Jenkins UI, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control JUnit report file contents.
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 confidenceThe Jenkins Flaky Test Handler Plugin 1.2.2 and earlier fails to escape JUnit test contents before rendering them in the Jenkins UI, creating a stored cross-site scripting (XSS) vulnerability. Attackers who can control JUnit report file contents can inject malicious scripts that execute when other users view the test results.
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
Flaky Test HandlerApplication
<= 1.2.2CVSS 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 Flaky Test Handler plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Flaky Test Handler' or check the plugin directory at $JENKINS_HOME/plugins for a folder named 'flaky-test-handler'Affected if The plugin appears in the installed plugins list
-
Determine installed plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find the Flaky Test Handler plugin and note the version number displayed in the 'Version' columnAffected if The version shown is 1.2.2 or earlier (e.g., 1.2.2, 1.2.1, 1.2.0)
-
Check if plugin is actively used in jobsReview Jenkins jobs for builds using the Flaky Test Handler plugin - look for job configurations that include 'Flaky Test Handler' in post-build actions or publishers, or check build directories under $JENKINS_HOME/jobs for any recorded flaky test resultsAffected if Any job is configured to publish results using this plugin or has historical flaky test data present
-
Assess user permissions for report uploadsNavigate to Jenkins > Manage Jenkins > Configure Global Security and review which users or groups have the ability to configure jobs or upload JUnit report files - check job-level permissions for report-related build stepsAffected if Users other than administrators can configure jobs or upload report files that would be processed by the plugin
A user is affected if the Flaky Test Handler plugin version is 1.2.2 or earlier AND the plugin is installed and potentially processing JUnit test data from users with upload permissions.
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 Flaky Test Handler Plugin version 1.2.3 or later which implements proper output escaping. Limit JUnit report upload permissions to trusted users as a compensating control until the upgrade is applied.
Fix this in Flaky Test Handler
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40342 — 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-2023-40342 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