CVE Intelligence
Medium Access control exploit reference

CVE-2020-15250 — Information disclosure in JUnit4

In JUnit4 from version 4.7 and before 4.13.1, the test rule TemporaryFolder contains a local information disclosure vulnerability. 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. This vulnerability impacts you if the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder, and the JUnit tests execute in an environment where the OS has other untrusted users. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. For Java 1.7 and higher users: this vulnerability is fixed in 4.13.1. For Java 1.6 and lower users: no patch is available, you must use the workaround below. If you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability. For more information, including an example of vulnerable code, see the referenced GitHub Security Advisory.

Published Oct 12, 2020 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 1.7% (30-day exploitation probability)+12
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
1.7%
ahead of 77% of scored CVEs · Oct 15, 2026
Affects
Apache Software Foundation
Pluto and 3 more
CVSS base
5.5
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — www.oracle.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Apache Software Foundation Pluto, Debian Debian Linux, Junit Junit4…).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Apache Software Foundation Pluto < 3.1.1 Vulnerable NIST National Vulnerability Database
Debian Debian Linux version 9.0 Vulnerable NIST National Vulnerability Database
Junit Junit4 ≥ 4.7 and < 4.13.1 Vulnerable NIST National Vulnerability Database
Junit-team Junit4 version < 4.13.1 Vulnerable CVE Program (cve.org) e CISA ADP
Oracle Communications Cloud Native Core Policy version 1.14.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.5 CVSS 3.1 Medium 1.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
4.4 CVSS 3.1 Medium 0.8 3.6 security-advisories@github.com via NIST National Vulnerability Database
4.4 CVSS 3.1 Medium — — GitHub_M via CVE Program (cve.org) e CISA ADP
1.9 CVSS 2.0 Low 3.4 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 5.5 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-732 · Incorrect Permission Assignment for Critical Resource

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 1.70%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Audit administrative actions and access to resources outside each user’s normal pattern.
endpoint telemetry (EDR)authentication logsapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · junit-team/junit4
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2020
  • CVE published
    Oct 12, 2020 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

39 on the record

Elsewhere on this site

Apache Software Foundation
every CVE for this vendor
Access control
same class
CWE-732
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-12996 A use-after-free in OpenVPN 2.6.0 through 2.6.20 and 2.7_alpha1 through 2.7.4 allows remote... Jul 30, 2026
  • CVE-2026-14355 ext/openssl: Memory corruption in openssl_encrypt with AES-WRAP-PAD Jul 3, 2026
  • CVE-2026-56968 Use of Uninitialized Resource in Gnu Sasl Jun 23, 2026
  • CVE-2026-49975 Apache HTTP Server: mod_http2 denial of service Jun 8, 2026
  • CVE-2026-9256 NGINX ngx_http_rewrite_module vulnerability May 22, 2026
  • CVE-2026-46333 ptrace: slightly saner 'get_dumpable()' logic May 15, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2020-15250 is "Information disclosure in JUnit4", rated Medium. It affects Pluto (Apache Software Foundation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 1.70% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.