CoverityApplication · Jenkins
CVE-2022-36921
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 missing permission check in Jenkins Coverity Plugin 1.11.4 and earlier allows attackers with Overall/Read permission 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 confidenceThe Jenkins Coverity Plugin versions 1.11.4 and earlier lack proper permission checks in certain endpoints. An attacker with only Overall/Read permissions (the most basic Jenkins permission) can invoke plugin functionality to connect to arbitrary URLs using credential IDs they obtain through separate enumeration, potentially capturing 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Confirm Coverity Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Coverity' in the list of installed plugins.Affected if The Coverity Plugin appears in the installed plugins list.
-
Identify the installed Coverity Plugin versionIn the Installed plugins tab, locate the Coverity Plugin and note the Version column value. Compare this version number to 1.11.4.Affected if The installed version is 1.11.4 or lower.
-
Verify plugin is enabledCheck the 'Enabled' checkbox status for the Coverity Plugin in the Installed plugins tab, or check if the plugin appears in the configuration pages (e.g., Manage Jenkins > Configure System, looking for Coverity-related configuration sections).Affected if The plugin is enabled and appears to be actively loaded by Jenkins.
-
Confirm Basic Read permission is granted to usersNavigate to Jenkins > Manage Jenkins > Manage Users and/or check the authorization matrix in Manage Jenkins > Configure Global Security. Verify which users or groups have the 'Overall/Read' permission.Affected if Non-admin users or service accounts have Overall/Read permissions enabled.
-
Check for stored credentials targetable by pluginNavigate to Manage Jenkins > Manage Credentials and review any credentials (such as API tokens, passwords, or secret files) stored in Jenkins domains. Note the credential IDs if present.Affected if Any credentials are stored in Jenkins credentials store, as these could be enumerated by an attacker using the vulnerable plugin endpoint.
If the Coverity Plugin is installed at version 1.11.4 or earlier, is enabled, and your Jenkins instance grants Overall/Read permissions to any non-admin users who could access the vulnerable endpoints, your environment is affected by this CVE.
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 Jenkins Coverity Plugin to a version newer than 1.11.4 that includes the missing permission check. If immediate upgrade is not possible, review Jenkins user permissions and disable the Coverity Plugin if not required.
Fix this in Coverity
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36921 — 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-36921 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