Flaky Test HandlerApplication · Jenkins
CVE-2022-28140
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.1 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
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 versions 1.2.1 and earlier contains an XML External Entity (XXE) vulnerability due to its XML parser not being configured to prevent XXE attacks. An attacker could exploit this by submitting specially crafted XML input containing external entity references, potentially allowing disclosure of confidential data, denial of service, or server-side request forgery.
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.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Identify if Flaky Test Handler plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-plugin-cli --list-plugins | grep -i flaky, or access /pluginManager/installed.jsp and search for Flaky Test HandlerAffected if The plugin appears in the installed plugins list
-
Determine the installed version of Flaky Test HandlerIn the Installed Plugins tab, locate Flaky Test Handler and note the Version column; or via REST API: curl -s http://<jenkins-url>/pluginManager/plugin/flaky-test-handler/api/json?pretty=trueAffected if Version is 1.2.1 or earlier, or the version field is absent (older installation)
-
Verify the plugin is actively processing XMLCheck if any jobs use the Flaky Test Handler post-build action or if XML report files (such as flaky-tests.xml) are being uploaded to Jenkins; review job configuration pages for Flaky Test Handler configurationAffected if The plugin is configured to parse XML reports in any job configuration
If Flaky Test Handler plugin version 1.2.1 or earlier is installed and is configured to parse XML reports in any job, the environment is vulnerable to CVE-2022-28140.
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.
dbcve · scopedUpgrade the Flaky Test Handler Plugin to version 1.2.2 or later, which includes proper XML parser configuration to prevent XXE attacks. If upgrading is not immediately possible, restrict plugin permissions and monitor for malicious XML submissions.
Flaky Test Handler Plugin version 1.2.2
- Log in to Jenkins as an administrator
- Navigate to 'Manage Jenkins' > 'Manage Plugins'
- Go to the 'Installed' tab
- Find 'Flaky Test Handler' in the list
- If an update is available, click 'Update' or install version 1.2.2
- Restart Jenkins if required to complete the update
- Verify the plugin shows version 1.2.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Flaky Test Handler
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28140 — 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-2022-28140 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