dbcve.org
SwampApplication · Jenkins

CVE-2022-25212

HIGH · 8.8 CVSS v3.1 Published 2022-02-15
Fix available
A fix is available. Upgrade to after 1.2.6 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 SWAMP Plugin 1.2.6 and earlier allows attackers to connect to an attacker-specified web server using attacker-specified credentials.

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

This is a CSRF vulnerability in Jenkins SWAMP Plugin 1.2.6 and earlier that allows authenticated users to be tricked into making unintended requests. An attacker can specify both a target web server URL and credentials, potentially causing the Jenkins instance to connect to malicious servers under the attacker's control.

MitigationUpgrade to a patched version of the SWAMP Plugin when available, and ensure Jenkins' global CSRF protection (CrumbIssuer) is enabled. Review plugin configurations for unauthorized connections.

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
SwampApplication
Affected:<= 1.2.6

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 SWAMP Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or check for swamp.hpi or swamp.jpi in the JENKINS_HOME/plugins directory
    Affected if SWAMP plugin appears in the installed plugins list or the plugin file exists in the plugins directory
  2. Check installed SWAMP Plugin version
    In Jenkins UI, locate SWAMP in the Installed plugins list and note the Version column; alternatively, examine the plugin's manifest (MANIFEST.MF) inside the swamp.hpi/jpi file
    Affected if Version is 1.2.6 or any version lower than 1.2.6 (e.g., 1.2.5, 1.2.0, 1.0)
  3. Confirm plugin is enabled and configured
    Navigate to Manage Jenkins > Configure System and look for SWAMP-related configuration sections, or check if the SWAMP plugin appears in the list of active plugins
    Affected if The SWAMP plugin is enabled and appears in active plugin configurations (CSRF exploitation requires the plugin to be active)
  4. Verify CSRF protection is active
    Go to Manage Jenkins > Configure Global Security and check if CSRF Protection (CrumbIssuer) is enabled
    Affected if CSRF protection is disabled - this increases the attack surface for this vulnerability

You are affected if the SWAMP Plugin is installed with version 1.2.6 or earlier and is enabled 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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.2.6
Interim mitigation

Upgrade to a patched version of the SWAMP Plugin when available, and ensure Jenkins' global CSRF protection (CrumbIssuer) is enabled. Review plugin configurations for unauthorized connections.

Recommended fix Moderate confidence

Latest available version of the SWAMP plugin in Jenkins Update Center (version > 1.2.6)

  1. 1. Log in to Jenkins as an administrator
  2. 2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. 3. Go to the 'Installed' tab
  4. 4. Locate the 'SWAMP' plugin in the list
  5. 5. If an update is available, select the plugin and click 'Download now and install after restart'
  6. 6. Alternatively, check the Jenkins Update Center for the latest SWAMP plugin version
  7. 7. After installation, restart Jenkins to apply the update
  8. 8. Verify the installed version is newer than 1.2.6

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Swamp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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