Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-15250 medium CVSS 4.4

Information Disclosure in Oracle Apache (CVE-2020-15250)

Summary

Vulnerability in Oracle Apache (CVE-2020-15250). Confidential information can be exposed externally. Exploitable via java.io.tmpdir. Mitigation: upgrade to 4.13.1 or later.

Original description

The description as published by the source.

Vulnerability

The JUnit4 test rule TemporaryFolder contains a local information disclosure vulnerability.

Example of vulnerable code:

public static class HasTempFolder {
    @Rule
    public TemporaryFolder folder = new TemporaryFolder();

    @Test
    public void testUsingTempFolder() throws IOException {
        folder.getRoot(); // Previous file permissions: `drwxr-xr-x`; After fix:`drwx------`
        File createdFile= folder.newFile("myfile.txt"); // unchanged/irrelevant file permissions
        File createdFolder= folder.newFolder("subfolder"); // unchanged/irrelevant file permissions
        // ...
    }
}

Impact

On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system.

This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability.

When analyzing the impact of this vulnerability, here are the important questions to ask:

  1. Do the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder?
    • If yes, this vulnerability impacts you, but only if you also answer 'yes' to question 2.
    • If no, this vulnerability does not impact you.
  2. Do the JUnit t…

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-2020-15250 has been found in Oracle Apache.
Attackers can target a specific entry point like java.io.tmpdir over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 4.4/10.
What to do: upgrade Oracle Apache to 4.13.1 or later.
If unsure, ask your IT team or search "Oracle Apache CVE-2020-15250" on the vendor's site.

CVE-2020-15250 (Oracle Apache) — CWE-200 / CVSS v3 4.4
Attack vector: local
Attack surface: java.io.tmpdir
Patched: 4.13.1 — 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.

❓ What is the problem

Information disclosure (CWE-200) exists in Oracle Apache. Attackers reach the vulnerable code path via java.io.tmpdir.

📍 Affected scope

Check the vendor advisory for the affected versions of Oracle Apache. Attack surface: java.io.tmpdir.

🔥 Severity

Severity: Medium (CVSS 4.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 4.13.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Apache' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'Apache' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で Apache を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade Oracle Apache to 4.13.1

    ステージング環境で 4.13.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Maven junit:junit
[{"type":"ECOSYSTEM","events":[{"introduced":"4.7"},{"fixed":"4.13.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details