dbcve.org
RequestsApplication · Jenkins

CVE-2021-21675

MEDIUM · 6.5 CVSS v3.1 Published 2021-06-30
Fix available
A fix is available. Upgrade to after 2.2.12 or later.
See remediation →
72/100
Remediation priority · Elevated
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 requests-plugin Plugin 2.2.12 and earlier allows attackers to create requests and/or have administrators apply pending requests.

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 the Jenkins requests-plugin versions 2.2.12 and earlier allows remote attackers to create arbitrary requests or force administrators to apply pending requests without their knowledge or consent, potentially leading to unauthorized configuration changes.

MitigationUpdate the Jenkins requests-plugin to a version later than 2.2.12 which includes CSRF protection tokens, and review any requests that may have been created or applied during the vulnerable period.

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
RequestsApplication
Affected:<= 2.2.12

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checks

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

  1. Identify if Jenkins requests-plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://[jenkins-url] list-plugins
    Affected if The requests-plugin appears in the installed plugins list
  2. Check the installed version of requests-plugin
    In Jenkins UI, find requests-plugin in the Installed tab and note the version number. Alternatively, check the plugin's .jpi or .hpi file in JENKINS_HOME/plugins/ directory for the version manifest
    Affected if The installed version is 2.2.12 or earlier (e.g., 2.2.12, 2.2.11, 2.2.10, etc.)
  3. Verify the plugin is actively loaded
    Check Jenkins system log or access the Jenkins CLI: java -jar jenkins-cli.jar -s http://[jenkins-url] plugin-dependent -name requests
    Affected if The plugin loads without errors and is listed as a dependency or active plugin

If the requests-plugin is installed and its version is 2.2.12 or earlier, the environment is affected by this CSRF vulnerability.

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 2.2.12
Interim mitigation

Update the Jenkins requests-plugin to a version later than 2.2.12 which includes CSRF protection tokens, and review any requests that may have been created or applied during the vulnerable period.

Fix this in Requests Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-21675 — 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-2021-21675 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