dbcve.org
JenkinsApplication

CVE-2023-43497

HIGH · 8.1 CVSS v3.1 Published 2023-09-20
Fix available
A fix is available. Upgrade to 2.414.2 / 2.424 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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
In Jenkins 2.423 and earlier, LTS 2.414.1 and earlier, processing file uploads using the Stapler web framework creates temporary files in the default system temporary directory with the default permissions for newly created files, potentially allowing attackers with access to the Jenkins controller file system to read and write the files before they are used.

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

In Jenkins 2.423 and earlier and LTS 2.414.1 and earlier, the Stapler web framework creates temporary files in the system's default temporary directory during file upload processing. These files are created with default OS permissions for new files, allowing attackers with filesystem access to the Jenkins controller to read or modify these temporary files before they are processed.

MitigationUpgrade Jenkins to version 2.424 or later (or LTS 2.414.2 or later) which implements secure temporary file handling, or configure Jenkins to use a dedicated temporary directory with restricted permissions.

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
JenkinsApplication
Affected:< 2.414.2< 2.424

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Check installed Jenkins version
    Access Jenkins web UI /about/ page, or run 'java -jar jenkins.war --version' from the Jenkins installation directory, or check the 'jenkins.install.UpgradedFromInitialRun' file in JENKINS_HOME if available
    Affected if Version is below 2.414.2 (LTS) or below 2.424 (weekly)
  2. Identify Jenkins temporary directory
    Check Java system property 'java.io.tmpdir' - run 'System.getProperty("java.io.tmpdir")' via Jenkins script console (Manage Jenkins > Script Console) or check the OS default temp directory (typically /tmp on Linux, C:\Users\...\AppData\Local\Temp on Windows)
    Affected if Using the system's default temporary directory (not a custom directory configured with restricted permissions)
  3. Verify temporary file permissions
    Upload a test file through Jenkins (e.g., via job configuration file parameter or plugin upload) and immediately check the permissions of any newly created files in the temp directory using 'ls -la' on Linux or 'icacls' on Windows
    Affected if Files are created with default OS permissions allowing other local users read or write access

User is affected if Jenkins version is below 2.414.2 or below 2.424 AND the default system temporary directory is being used without additional access restrictions.

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 2.414.2 / 2.424 or later
Fixed in 2.414.22.424
Interim mitigation

Upgrade Jenkins to version 2.424 or later (or LTS 2.414.2 or later) which implements secure temporary file handling, or configure Jenkins to use a dedicated temporary directory with restricted permissions.

Recommended fix High confidence

Jenkins 2.424 (weekly) or Jenkins 2.414.2 (LTS)

  1. Back up your Jenkins home directory and configuration before upgrading
  2. Download and install Jenkins 2.424 or later for weekly releases, OR Jenkins 2.414.2 or later for LTS releases
  3. Restart Jenkins service to apply the update
  4. Verify Jenkins starts successfully and check the Jenkins version at /about/
Caveat Review Jenkins LTS upgrade guide for any compatibility considerations before upgrading

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

Fix this in Jenkins Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.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-2023-43497 — 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-2023-43497 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