Authorization Flaw in org.jenkins-ci.main:jenkins-core (CVE-2023-27903)
Summary
Vulnerability in org.jenkins-ci.main:jenkins-core (CVE-2023-27903). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.394 or later.
Original description
The description as published by the source.
When triggering a build from the Jenkins CLI, Jenkins creates a temporary file on the controller if a file parameter is provided through the CLI’s standard input.
Jenkins 2.393 and earlier, LTS 2.375.3 and earlier, and , and LTS prior to 2.387.1 creates this temporary file in the default temporary directory with the default permissions for newly created files.
If these permissions are overly permissive, they may allow attackers with access to the Jenkins controller file system to read and write the file before it is used in the build.
This vulnerability only affects operating systems using a shared temporary directory for all users (typically Linux). Additionally, the default permissions for newly created files generally only allows attackers to read the temporary file.
Jenkins 2.394, LTS 2.375.4, and LTS 2.387.1 creates the temporary file with more restrictive permissions.
As a workaround, you can set a different path as your default temporary directory using the Java system property java.io.tmpdir, if you’re concerned about this issue but unable to immediately update Jenkins.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2023-27903 has been found in org.jenkins-ci.main:jenkins-core.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.jenkins-ci.main:jenkins-core to 2.394 or later.
If unsure, ask your IT team or search "org.jenkins-ci.main:jenkins-core CVE-2023-27903" on the vendor's site.
CVE-2023-27903 (org.jenkins-ci.main:jenkins-core) — CWE-863
Attack vector: local / no user interaction
Patched: 2.394 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in org.jenkins-ci.main:jenkins-core.
Check the vendor advisory for the affected versions of org.jenkins-ci.main:jenkins-core.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.394.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.jenkins-ci.main:jenkins-core を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.jenkins-ci.main:jenkins-core to 2.394ステージング環境で 2.394 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web jenkins.io
- web github.com
- web github.com