dbcve.org
Scm HttpclientApplication · Jenkins

CVE-2022-41249

HIGH · 8.8 CVSS v3.1 Published 2022-09-21
Fix available
A fix is available. Upgrade to after 1.5 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 SCM HttpClient Plugin 1.5 and earlier allows attackers to connect to an attacker-specified HTTP server 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 confidence

A CSRF vulnerability in Jenkins SCM HttpClient Plugin 1.5 and earlier allows authenticated users to be tricked into making requests that connect to attacker-controlled HTTP servers using credentials stored in Jenkins, enabling credential theft. The attacker leverages the victim's authenticated session to specify credential IDs and capture the credential data via their server.

MitigationUpdate Jenkins SCM HttpClient Plugin to version 1.6 or later. Review Jenkins credentials usage and revoke any potentially exposed credentials as a precaution.

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
Scm HttpclientApplication
Affected:<= 1.5

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. Check if SCM HttpClient Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed, or use Jenkins CLI: java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins | grep -i scmhttpclient
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and find 'SCM HttpClient' in the list to see the version column. Alternatively, check the plugin's manifest at: $JENKINS_HOME/plugins/scm-httpclient-plugin/META-INF/MANIFEST.MF
    Affected if Version is 1.5 or earlier
  3. Verify Jenkins credentials exist
    Go to Manage Jenkins > Manage Credentials. Review any credentials stored globally or within specific domains. Note the credential IDs and types (username/password, secret text, etc.)
    Affected if Any credentials are stored in Jenkins that could be accessed by the plugin
  4. Confirm plugin is in use or configurable
    Check job configurations for any jobs using SCM HttpClient plugin functionality, or review Jenkins system configuration (Manage Jenkins > Configure System) for SCM HttpClient plugin settings
    Affected if The plugin is actively configured or used in any job or system configuration

You are affected if the SCM HttpClient Plugin is installed at version 1.5 or earlier AND Jenkins credentials are stored in your 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.5
Interim mitigation

Update Jenkins SCM HttpClient Plugin to version 1.6 or later. Review Jenkins credentials usage and revoke any potentially exposed credentials as a precaution.

Recommended fix Moderate confidence

SCM HttpClient Plugin version 1.6 or later

  1. Navigate to the Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Click on the 'Installed' tab
  4. Locate the 'SCM HttpClient Plugin' in the list
  5. Check if the installed version is 1.5 or earlier
  6. If vulnerable, click 'Check now' for updates or manually download the fixed version from the Jenkins plugin repository
  7. Install version 1.6 or later which contains the security fix
  8. Restart Jenkins if required to complete the plugin update

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

Fix this in Scm Httpclient Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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