dbcve.org
Security InspectorApplication · Jenkins

CVE-2022-41236

HIGH · 8.8 CVSS v3.1 Published 2022-09-21
Fix available
A fix is available. Upgrade to after 117.v6eecc36919c2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
A cross-site request forgery (CSRF) vulnerability in Jenkins Security Inspector Plugin 117.v6eecc36919c2 and earlier allows attackers to replace the generated report stored in a per-session cache and displayed to authorized users at the .../report URL with a report based on attacker-specified report generation options.

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 confidence

A CSRF vulnerability in Jenkins Security Inspector Plugin versions 117.v6eecc36919c2 and earlier allows authenticated attackers to trick authorized users into replacing the cached report displayed at the .../report URL with a report generated using attacker-specified options. Since the malicious report is then presented to legitimate users, this could lead to misleading or crafted security findings being presented as authoritative.

MitigationUpdate Jenkins Security Inspector Plugin to a version newer than 117.v6eecc36919c2 once available, and ensure Jenkins' built-in CSRF protection (crumb) is enabled.

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
Security InspectorApplication
Affected:<= 117.v6eecc36919c2

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Security Inspector plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: `java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins` and look for 'security-inspector' or 'Security Inspector' in the output
    Affected if The plugin does not appear in the installed plugins list, meaning the plugin is not present and this vulnerability does not apply
  2. Determine the installed version of Security Inspector plugin
    In the Installed plugins tab, locate Security Inspector and note the version number displayed. Alternatively, examine the plugin's manifest file at `$JENKINS_HOME/plugins/security-inspector/META-INF/MANIFEST.MF` and find the Implementation-Version attribute
    Affected if The installed version is 117.v6eecc36919c2 or any version lower (e.g., 116.v..., 115.v...), indicating the plugin is vulnerable
  3. Confirm the report feature is accessible
    Attempt to access the Security Inspector report URL at `.../security-inspector/report` or check if the plugin's report functionality is enabled via Jenkins > Manage Jenkins > Security Inspector configuration
    Affected if The report URL returns a valid response or the feature is configured, meaning the vulnerable functionality is active in the environment
  4. Check if the Jenkins CSRF protection is enabled
    Navigate to Manage Jenkins > Configure Global Security and verify if the 'Prevent Cross Site Request Forgery exploits' crumb option is enabled under the CSRF Protection section
    Affected if CSRF protection is disabled (not recommended), which would make exploitation easier, though the vulnerability exists regardless of this setting

You are affected if the Jenkins Security Inspector plugin is installed with version 117.v6eecc36919c2 or earlier and the report feature is accessible in your Jenkins instance.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 117.v6eecc36919c2
Interim mitigation

Update Jenkins Security Inspector Plugin to a version newer than 117.v6eecc36919c2 once available, and ensure Jenkins' built-in CSRF protection (crumb) is enabled.

Fix this in Security Inspector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-41236 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-41236 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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