TicsApplication · Jenkins
CVE-2021-21613
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 TICS Plugin 2020.3.0.6 and earlier does not escape TICS service responses, resulting in a cross-site scripting (XSS) vulnerability exploitable by attackers able to control TICS service response content.
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 TICS Plugin fails to escape TICS service response content before rendering it in the Jenkins UI, allowing stored XSS injection. Attackers who control the TICS service response can inject malicious JavaScript that executes in victim users' browsers when they view the plugin output.
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
TicsApplication
<= 2020.3.0.6CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Jenkins TICS Plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'TICS' or 'TICS Plugin', or inspect the plugin directory $JENKINS_HOME/plugins/ for a tics or tics-plugin folder.Affected if The TICS Plugin appears in the list of installed plugins.
-
Determine the installed TICS Plugin versionIn Jenkins plugin manager, click on the TICS Plugin and note the version number displayed, or check the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin's .hpi file in $JENKINS_HOME/plugins/.Affected if The installed version is 2020.3.0.6 or any lower version.
-
Check if TICS service connection is configuredNavigate to the Jenkins configuration page for the TICS Plugin (typically under Manage Jenkins or in the job configuration if used in pipelines) and look for TICS service URL or connection settings.Affected if A TICS service URL or endpoint is configured and the plugin is actively retrieving or displaying TICS data.
-
Verify if TICS output is rendered in Jenkins UIView a Jenkins job that uses the TICS Plugin or navigate to any page where TICS report data is displayed. Check if the plugin renders response content from the TICS service in the browser.Affected if The plugin displays TICS service response data or reports within Jenkins views.
If the installed TICS Plugin version is 2020.3.0.6 or lower and the plugin is used to display TICS service output in Jenkins, the environment is affected by this stored XSS vulnerability.
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 dataUpdate to a patched version of the TICS Plugin. Until then, restrict access to TICS service configuration and consider adding Content-Security-Policy headers to mitigate script execution.
Fix this in Tics
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21613 — 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-2021-21613 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