TapApplication · Jenkins
CVE-2023-41940
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 TAP Plugin 2.3 and earlier does not escape TAP file contents, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers able to control TAP 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 TAP Plugin 2.3 and earlier fails to escape TAP file contents before rendering them in the web interface, creating a stored XSS vulnerability. Attackers who can control or influence TAP file contents processed by the plugin can inject malicious JavaScript that executes in the browsers of users viewing TAP 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
TapApplication
<= 2.3CVSS 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.
-
Check if Jenkins TAP Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'TAP' in the filter, or check $JENKINS_HOME/plugins for the tap directoryAffected if The TAP Plugin is present in the Jenkins plugins directory
-
Determine installed TAP Plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed, locate the TAP Plugin and note the version number displayed in the version columnAffected if The installed version is 2.3 or lower, or if no version is shown but the plugin is present and older than 2.4
-
Check for TAP test result archives or builds using TAP PluginReview recent build histories and look for TAP test result archives (TAP files) being archived, or check job configurations for 'TAP Publisher' or similar TAP-related build stepsAffected if TAP files are being processed and their results are being published/viewed in Jenkins web interface
-
Verify TAP results are viewable in web interfaceNavigate to build pages and check if TAP test results are displayed (look for TAP test result links or embedded TAP output)Affected if TAP test results are rendered in the Jenkins web interface where unescaped content could execute
-
Identify who can upload or modify TAP filesReview job configurations and permissions for jobs that process TAP files - check which users or groups have the ability to create or modify TAP input filesAffected if Users with limited or untrusted permissions can supply or modify TAP file contents that get processed by the plugin
A user is affected if the Jenkins TAP Plugin version 2.3 or earlier is installed AND TAP test results are being displayed in the web interface, allowing potential injection of malicious JavaScript through TAP file contents.
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 a patched version of the Jenkins TAP Plugin when available. Until then, restrict who can provide or modify TAP file inputs to the plugin and consider disabling the plugin if untrusted TAP files are being processed.
Fix this in Tap
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41940 — 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-41940 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