JiratestresultreporterApplication · Jenkins
CVE-2022-28136
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 JiraTestResultReporter Plugin 165.v817928553942 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials.
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 the Jenkins JiraTestResultReporter Plugin versions 165.v817928553942 and earlier allows authenticated users to be tricked into connecting to attacker-specified URLs using attacker-specified credentials, potentially enabling credential theft or unauthorized API connections.
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
JiratestresultreporterApplication
<= 165.v817928553942CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Access Jenkins plugin management interfaceLog into Jenkins and navigate to Manage Jenkins > Manage PluginsAffected if You have access to the Jenkins administration dashboard
-
Locate JiraTestResultReporter pluginIn the Manage Plugins page, go to the 'Installed' tab and search for 'JiraTestResultReporter' in the plugin listAffected if The JiraTestResultReporter plugin appears in the installed plugins list
-
Identify installed plugin versionRead the version number displayed next to the JiraTestResultReporter plugin name in the installed plugins tableAffected if You can read a version number for the plugin
-
Compare version to affected rangeCompare the installed version number to 165.v817928553942. Any version equal to or lower than 165.v817928553942 is affectedAffected if The installed version is 165.v817928553942 or any earlier version (for example: 164.v817928553941, 163.v817928553940, etc.)
If the JiraTestResultReporter plugin is installed and its version is 165.v817928553942 or earlier, the environment is affected by this CSRF 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.
dbcve · scopedUpgrade JiraTestResultReporter Plugin to version 165.v817928553942 or later to remediate the CSRF vulnerability.
166.v817928553942 or later
- Navigate to Manage Jenkins > Manage Plugins
- Go to the 'Installed' tab
- Locate 'JiraTestResultReporter' in the list
- If an update is available, select the plugin and click 'Update'
- Restart Jenkins if required
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Jiratestresultreporter
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28136 — 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-28136 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