CVE-2020-15250: Information disclosure in JUnit4

Published Oct 12, 2020
·
Updated

Vulnerability

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

Example of vulnerable code: java 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 tests ever execute in an environment where the OS has other untrusted users. This may apply in CI/CD environments but normally won't be 'yes' for personal developer machines. - If yes, and you answered 'yes' to question 1, this vulnerability impacts you. - If no, this vulnerability does not impact you.

Patches

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. - Java 1.7 and higher users: this vulnerability is fixed in 4.13.1. - Java 1.6 and lower users: no patch is available, you must use the workaround below.

Workarounds

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.

References - CWE-200: Exposure of Sensitive Information to an Unauthorized Actor - Fix commit https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae

Similar Vulnerabilities - Google Guava - https://github.com/google/guava/issues/4011 - Apache Ant - https://nvd.nist.gov/vuln/detail/CVE-2020-1945 - JetBrains Kotlin Compiler - https://nvd.nist.gov/vuln/detail/CVE-2020-15824

For more information If you have any questions or comments about this advisory, please pen an issue in junit-team/junit4.

Other sources

In JUnit4 before version 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.

References https://github.com/junit-team/junit4/blob/7852b90cfe1cea1e0cdaa19d490c83f0d8684b50/doc/ReleaseNotes4.13.1.md https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp https://junit.org/junit4/javadoc/4.13/org/junit/rules/TemporaryFolder.html

— Red Hat

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.

JUnit4 could allow a local attacker to obtain sensitive information, caused by a flaw in test rule TemporaryFolder. By sending a specially crafted request, an attacker could exploit this vulnerability to obtain sensitive information.

— IBM

Affected Software

18 affected componentsFixes available
JUnit JUnit4>=4.7<4.13.1
Debian Debian Linux=9.0
Apache Pluto<3.1.1
Oracle Communications Cloud Native Core Policy=1.14.0
redhat/junit<4.13.1
4.13.1
maven/junit:junit>=4.7<4.13.1
4.13.1
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0
alpine/junit<4.13.1-r0
4.13.1-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/junit to a version that resolves this vulnerability.

    Fixed in 4.13.1
  2. Upgrade

    Upgrade maven/junit:junit to a version that resolves this vulnerability.

    Fixed in 4.13.1
  3. Upgrade

    Upgrade alpine/junit to a version that resolves this vulnerability.

    Fixed in 4.13.1-r0
  4. Upgrade

    Upgrade junit-team/junit4 to a version that resolves this vulnerability.

    Fixed in 4.13.1
  5. Configuration

    Set the java.io.tmpdir system environment variable to a directory exclusively owned by the executing user if unable to patch or when running on Java 1.6.

    Java temporary directory java.io.tmpdir = A directory exclusively owned by the executing user

Event History

Oct 12, 2020
CVE Published
12:00 AM
Data Sourced
12:00 AM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·05:33 PM
Data Sourced
via GitHub·05:33 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·05:55 PM
Data Sourced
via MITRE·05:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·06:15 PM
DescriptionSeverityAffected Software
Oct 13, 2020
Data Sourced
via Red Hat·12:20 PM
DescriptionSeverityAffected Software
May 2, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2020-15250?

CVE-2020-15250 is classified with a medium severity due to its potential for local information disclosure.

2

How do I fix CVE-2020-15250?

To fix CVE-2020-15250, you should upgrade JUnit4 to version 4.13.1 or later.

3

Which systems are affected by CVE-2020-15250?

CVE-2020-15250 affects JUnit4 versions prior to 4.13.1 on Unix-like systems.

4

What types of files are at risk with CVE-2020-15250?

Files and directories written to the system's temporary directory are at risk due to CVE-2020-15250.

5

Can CVE-2020-15250 affect applications using JUnit4?

Yes, applications using affected versions of JUnit4 can be impacted by the local information disclosure vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203