Skip to content
Fencer Vulns
medium 4.4

CVE-2020-15250 json

Information disclosure in JUnit4

published 2020-10-12 6 y ago modified 2026-10-07 32 d ago also GHSA-269g-pwp5-87pp , EUVD-2020-1400

cvss
4.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.7%
EPSS 1.7% chance of exploitation in 30 days, percentile 77%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven junit:junit 4.13.1
  • junit junit4 4.13.1
  • apache pluto 3.1.1
  • junit4 Debian 14, Debian 13, Debian 12 4.13.1-1

debian advisories DEBIAN-CVE-2020-15250

  • junit4 Ubuntu 16.04 LTS 4.12-4ubuntu1.1
  • junit4 Ubuntu 18.04 LTS 4.12-8~18.04.1
  • junit4 Ubuntu 20.04 LTS 4.12-8ubuntu0.20.04.1

ubuntu advisories UBUNTU-CVE-2020-15250

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • junit Alpine 3.24, Alpine 3.23, Alpine 3.22 +9 more 4.13.1-r0

alpine advisories ALPINE-CVE-2020-15250

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • junit Azure Linux 3.0 4.13-7

azure linux advisories AZL-41745

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-15250 updated cvss 4.0

junit4: TemporaryFolder is shared between all users across system which could result in information disclosure

  • Red Hat Enterprise Linux 7 junit, junit-demo, junit-manual, junit-javadoc
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 junit, junit-manual, junit-javadoc
    affected: no fix available “Fix deferred”
  • Red Hat Fuse 7.11
    fixed: vendor fix RHSA-2022:5532
  • Red Hat Data Grid 8 infinispan-server-testdriver-junit4 Red Hat Enterprise Linux 6 junit4, junit4-demo, junit4-manual, junit4-javadoc Red Hat JBoss Enterprise Application Platform 6 surefire-junit4 surefire-junit4, powermock-module-junit4 powermock-module-junit4, powermock-module-junit4-common powermock-module-junit4-common Red Hat JBoss Fuse 6 pax-exam-junit4, junit4-ant junit4-ant, jmock-junit4 jmock-junit4, common-junit4 common-junit4, common-junit48 common-junit48, surefire-junit4 surefire-junit4, +3 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
32 d ago

Exploit prediction

1.70% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 4.4 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:P/I:N/A:N
GitHub 3.1 4.4 CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven junit:junit
>=4.7, <4.13.1
4.13.1

Affected products

  • junit-team junit4

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-732 Incorrect Permission Assignment for Critical Resource

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.