Security Resilience

CVE-2023-43498

Jenkins ≤ 2.414.2

Published
20 September 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS Score 0.0097 61th percentile
Risk Priority 62 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-43498 is a high-severity Insecure Temporary File (CWE-377) vulnerability in Jenkins Jenkins. Its CVSS base score is 8.1 (High).

Operationally, ranked in the top 39% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

In Jenkins 2.423 and earlier, LTS 2.414.1 and earlier, processing file uploads using MultipartFormDataParser 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…

more

file system to read and write the files before they are used.

CWE(s)
NVD-CWE-noinfoCWE-377

Related Threats

CVEs Like This One

CVE-2025-67635Same product: Jenkins Jenkins
CVE-2024-47804Same product: Jenkins Jenkins
CVE-2026-53438Same product: Jenkins Jenkins
CVE-2023-43494Same product: Jenkins Jenkins
CVE-2026-84650Same product: Jenkins Jenkins
CVE-2026-53440Same product: Jenkins Jenkins
CVE-2025-67638Same product: Jenkins Jenkins
CVE-2025-59475Same product: Jenkins Jenkins
CVE-2023-43496Same product: Jenkins Jenkins
CVE-2025-67639Same product: Jenkins Jenkins

Affected Assets

jenkins
jenkins
≤ 2.414.2 · ≤ 2.424

Mitigating Controls

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match
blocks

Secure development life cycle mandates secure handling of temporary files during design and coding.

A.8.26 Application security requirements partial match
blocks

A.8.26 only requires that security requirements (including resilience against injections or input validation) be identified and specified during development or acquisition; it does not itself enforce, implement or configure any mechanism that stops an insecure temporary file from being created or exploited.

A.8.27 Secure system architecture and engineering principles partial match
blocks

Secure system architecture principles discourage insecure temporary-file patterns but do not directly address them.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require safe temporary-file APIs and permissions.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing can detect insecure temporary files but does not prevent their creation.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-377, a class-level weakness. Rules are authored against its narrower children: CWE-379.

References