dbcve.org
ThreadfixApplication · Jenkins

CVE-2022-34209

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-23
Fix available
A fix is available. Upgrade to after 1.5.4 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 ThreadFix Plugin 1.5.4 and earlier allows attackers to connect to an attacker-specified URL.

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

Cross-site request forgery (CSRF) vulnerability in Jenkins ThreadFix Plugin versions 1.5.4 and earlier allows authenticated or unauthenticated attackers to trick the Jenkins server into making HTTP requests to attacker-controlled URLs. This occurs because the plugin does not properly validate the origin of requests or implement CSRF tokens for its actions.

MitigationUpdate Jenkins ThreadFix Plugin to version 1.5.5 or later. Additionally, ensure Jenkins global security settings enforce CSRF protection (enable 'Prevent Cross Site Request Forgery exploits' checkbox).

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
ThreadfixApplication
Affected:<= 1.5.4

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. Verify ThreadFix plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar who-am-i (if available). Look for 'ThreadFix' in the plugin list.
    Affected if ThreadFix plugin is not listed in installed plugins, then the plugin is not affected because it is not present in the environment.
  2. Identify installed ThreadFix plugin version
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find ThreadFix and note the version number displayed. Alternatively, check the plugin's manifest file at WEB-INF/plugins/threadfix.jpi or .hpi if you have file system access.
    Affected if The installed version is 1.5.4 or earlier.
  3. Check Jenkins global CSRF protection setting
    Navigate to Jenkins > Manage Jenkins > Configure Global Security. Locate the 'Prevent Cross Site Request Forgery exploits' checkbox under the Security Configuration section.
    Affected if The CSRF protection checkbox is unchecked or disabled.
  4. Confirm plugin endpoint accessibility
    Review if the ThreadFix plugin REST API endpoints (/threadfix/ or similar paths under the Jenkins root) are accessible to unauthenticated users or allow requests without CSRF tokens, by inspecting the plugin's configuration page at Jenkins > Manage Jenkins > Configure System > ThreadFix section.
    Affected if The plugin is accessible to anonymous users or accepts requests without CSRF token validation.

The environment is affected if the ThreadFix plugin is installed at version 1.5.4 or earlier and the Jenkins global CSRF protection is disabled or the plugin accepts requests without validating CSRF tokens.

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.4
Interim mitigation

Update Jenkins ThreadFix Plugin to version 1.5.5 or later. Additionally, ensure Jenkins global security settings enforce CSRF protection (enable 'Prevent Cross Site Request Forgery exploits' checkbox).

Recommended fix High confidence

ThreadFix Plugin version 1.5.5

  1. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  2. Select the 'Installed' tab
  3. Locate the ThreadFix plugin in the list
  4. If version 1.5.4 or earlier is installed, click 'Update now' to upgrade to version 1.5.5 or later
  5. Restart Jenkins if required to complete the update

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

Fix this in Threadfix Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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