CoverityApplication · Jenkins
CVE-2022-36920
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 Coverity Plugin 1.11.4 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 confidenceThis is a CSRF (Cross-Site Request Forgery) vulnerability in Jenkins Coverity Plugin versions 1.11.4 and earlier. The flaw allows authenticated attackers to trick Jenkins users into making unintended requests that connect to attacker-controlled URLs using attacker-specified credentials IDs, enabling capture of stored Jenkins credentials.
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
CoverityApplication
<= 1.11.4CVSS 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.
-
Verify Coverity Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Coverity' in the list of installed pluginsAffected if Coverity Plugin appears in the installed plugins list
-
Check Coverity Plugin versionIn the Installed plugins list, locate the Coverity Plugin and note the Version column. Compare this version number to 1.11.4Affected if The installed version is 1.11.4 or earlier
-
Inspect configured Coverity credentialsNavigate to Manage Jenkins > Manage Credentials. Review any credentials entries associated with the Coverity Plugin (typically shown under the 'Coverity' domain or with Coverity-related descriptions)Affected if Credentials exist in the Coverity credentials store and could be targeted by the CSRF attack
-
Check for unauthorized credential IDsReview any Coverity-related job configurations or global settings for credential IDs that connect to unexpected or unknown URLs, or check the Jenkins logs for any suspicious connections to external URLsAffected if Credential IDs are configured that connect to URLs not controlled by your organization
A user is affected if the Coverity Plugin is installed at version 1.11.4 or earlier and has credentials configured in Jenkins that could be leveraged via CSRF to connect to attacker-controlled URLs.
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 Jenkins Coverity Plugin to a version newer than 1.11.4 and review Jenkins credentials for unauthorized access or exfiltration.
Fix this in Coverity
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36920 — 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-36920 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