First published: Mon Oct 12 2020(Updated: )
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 <a href="https://github.com/junit-team/junit4/blob/7852b90cfe1cea1e0cdaa19d490c83f0d8684b50/doc/ReleaseNotes4.13.1.md">https://github.com/junit-team/junit4/blob/7852b90cfe1cea1e0cdaa19d490c83f0d8684b50/doc/ReleaseNotes4.13.1.md</a> <a href="https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae">https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae</a> <a href="https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp">https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp</a> <a href="https://junit.org/junit4/javadoc/4.13/org/junit/rules/TemporaryFolder.html">https://junit.org/junit4/javadoc/4.13/org/junit/rules/TemporaryFolder.html</a>
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/junit | <4.13.1 | 4.13.1 |
IBM Security Risk Manager on CP4S | <=CP4S 1.7.2.0 | |
JUnit | >=4.7<4.13.1 | |
Debian | =9.0 | |
Apache Pluto | <3.1.1 | |
Oracle Communications Cloud Native Core Policy | =1.14.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-15250 is classified with a medium severity due to its potential for local information disclosure.
To fix CVE-2020-15250, you should upgrade JUnit4 to version 4.13.1 or later.
CVE-2020-15250 affects JUnit4 versions prior to 4.13.1 on Unix-like systems.
Files and directories written to the system's temporary directory are at risk due to CVE-2020-15250.
Yes, applications using affected versions of JUnit4 can be impacted by the local information disclosure vulnerability.