Xray Test Management For JiraApplication · Jenkins
CVE-2021-21652
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Xray - Test Management for Jira Plugin 2.4.0 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
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 confidenceA CSRF vulnerability in Jenkins Xray - Test Management for Jira Plugin versions 2.4.0 and earlier allows authenticated attackers to trigger Jenkins to connect to attacker-specified URLs using stored credential IDs. The attacker can capture these credentials by specifying a malicious server URL, exploiting the lack of proper CSRF token validation on the affected form submissions.
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
Xray Test Management For JiraApplication
<= 2.4.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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 if Xray - Test Management for Jira plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Xray' or 'Xray - Test Management for Jira'. Alternatively, check the $JENKINS_HOME/plugins/ directory for files starting with 'xray' or 'xray-test-management'.Affected if The plugin appears in the installed plugins list
-
Determine the installed version of the Xray pluginIn the Jenkins UI, click on the Xray plugin entry in the Installed plugins tab to view its version. If using CLI, examine the plugin's MANIFEST.MF or .jpi file in the plugins directory for the Version attribute.Affected if A version number is displayed that is less than or equal to 2.4.0
-
Confirm the plugin is active and configuredNavigate to Manage Jenkins > Configure System and look for Xray configuration sections. Also check any Jenkins jobs or pipelines that may reference Xray functionality.Affected if The plugin has active configuration or is referenced in job configurations
You are affected if the Xray - Test Management for Jira plugin is installed and its version is 2.4.0 or earlier, regardless of whether it has active configurations.
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 the Xray - Test Management for Jira Plugin to a version newer than 2.4.0. Until then, restrict plugin permissions, review stored credentials, and consider disabling the plugin if not actively used.
Fix this in Xray Test Management For Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21652 — 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-21652 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