P4Application · Jenkins
CVE-2021-21655
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 P4 Plugin 1.11.4 and earlier allows attackers to connect to an attacker-specified Perforce server using attacker-specified username and password.
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 vulnerability in Jenkins P4 Plugin that allows attackers to trick authenticated users into connecting to a malicious Perforce server with attacker-specified credentials. The lack of CSRF protection on the relevant plugin endpoints enables cross-site request forgery attacks.
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
P4Application
<= 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/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.
-
Verify P4 Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'P4' in the filter. Confirm the P4 Plugin appears in the list of installed plugins.Affected if P4 Plugin is not installed, the vulnerability does not apply.
-
Locate the installed version of P4 PluginIn the same Installed Plugins tab, find the P4 Plugin entry and note the version number displayed in the Version column.Affected if Unable to determine the version from the plugin manager interface.
-
Compare version against affected rangeCompare the installed P4 Plugin version to the affected range: any version <= 1.11.4 is vulnerable. For example, versions 1.11.4, 1.11.3, 1.11.2, 1.11.1, 1.11.0, 1.10.x, and earlier are all affected.Affected if The installed version is 1.11.4 or lower.
-
Confirm CSRF protection statusNavigate to Manage Jenkins > Configure Global Security > Security > CSRF Protection. Verify whether crumb validation is enabled. Note: The vulnerability exists because the plugin itself lacks proper crumb handling, but confirming global CSRF protection is enabled provides context.Affected if Global CSRF protection being disabled increases exposure but does not change whether the P4 plugin itself is vulnerable.
The environment is affected if the Jenkins P4 Plugin is installed with version 1.11.4 or any earlier version.
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 P4 Plugin to version 1.11.5 or later which includes proper CSRF protection (crumb validation). If upgrading is not possible, restrict access to Jenkins to trusted users only.
Fix this in P4
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21655 — 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-2021-21655 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