MediumGHSA-5mcr-gq6c-3hq2CVE-2021-21290

Local Information Disclosure Vulnerability in Netty on Unix-Like systems

Published 8 Feb 2021 · Updated 10 Sept 2026

Is your project on an affected io.netty:netty-codec-http?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=4.0.0 <4.1.59.Final
Fixed in
4.1.59.Final
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=io.netty:netty-codec-http -DdepVersion=4.1.59.Final -DforceVersion=true
Affected
All versions
Fixed in
No fix released
Affected
All versions
Fixed in
No fix released

Details

Impact

When netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled.

The CVSSv3.1 score of this vulnerability is calculated to be a 6.2/10

Vulnerability Details

On unix-like systems, the temporary directory is shared between all user. As such, writing to this directory using APIs that do not explicitly set the file/directory permissions can lead to information disclosure. Of note, this does not impact modern MacOS Operating Systems.

The method File.createTempFile on unix-like systems creates a random file, but, by default will create this file with the permissions -rw-r--r--. Thus, if sensitive information is written to this file, other local users can read this information.

This is the case in netty's AbstractDiskHttpData is vulnerable.

https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/codec-http/src/main/java/io/netty/handler/codec/http/multipart/AbstractDiskHttpData.java#L80-L101

AbstractDiskHttpData is used as a part of the DefaultHttpDataFactory class which is used by HttpPostRequestDecoder / HttpPostMultiPartRequestDecoder.

You may be affected by this vulnerability your project contains the following code patterns:

channelPipeline.addLast(new HttpPostRequestDecoder(...));
channelPipeline.addLast(new HttpPostMultiPartRequestDecoder(...));

Patches

This has been patched in version 4.1.59.Final.

Workarounds

Specify your own java.io.tmpdir when you start the JVM or use DefaultHttpDataFactory.setBaseDir(...) to set the directory to something that is only readable by the current user.

References

Similar Vulnerabilities

Similar, but not the same.

  • JUnit 4 - https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp
  • 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:

  • Open an issue in netty
  • Email us [here](mailto:netty-security@googlegroups.com)

Original Report

> Hi Netty Security Team, > > I've been working on some security research leveraging custom CodeQL queries to detect local information disclosure vulnerabilities in java applications. This was the result from running this query against the netty project: > https://lgtm.com/query/7723301787255288599/ > > Netty contains three local information disclosure vulnerabilities, so far as I can tell. > > One is here, where the private key for the certificate is written to a temporary file. > > https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/handler/src/main/java/io/netty/handler/ssl/util/SelfSignedCertificate.java#L316-L346 > > One is here, where the certificate is written to a temporary file. > > https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/handler/src/main/java/io/netty/handler/ssl/util/SelfSignedCertificate.java#L348-L371 > > The final one is here, where the 'AbstractDiskHttpData' creates a temporary file if the getBaseDirectory() method returns null. I believe that 'AbstractDiskHttpData' is used as a part of the file upload support? If this is the case, any files uploaded would be similarly vulnerable. > > https://github.com/netty/netty/blob/e5951d46fc89db507ba7d2968d2ede26378f0b04/codec-http/src/main/java/io/netty/handler/codec/http/multipart/AbstractDiskHttpData.java#L91 > > All of these vulnerabilities exist because File.createTempFile(String, String) will create a temporary file in the system temporary directory if the 'java.io.tmpdir' system property is not explicitly set. It is my understanding that when java creates a file, by default, and using this method, the permissions on that file utilize the umask. In a majority of cases, this means that the file that java creates has the permissions: -rw-r--r--, thus, any other local user on that system can read the contents of that file. > > Impacted OS: > - Any OS where the system temporary directory is shared between multiple users. This is not the case for MacOS or Windows. > > Mitigation. > > Moving to the Files API instead will fix this vulnerability. > https://docs.oracle.com/javase/8/docs/api/java/nio/file/Files.html#createTempFile-java.nio.file.Path-java.lang.String-java.lang.String-java.nio.file.attribute.FileAttribute...- > > This API will explicitly set the posix file permissions to something safe, by default. > > I recently disclosed a similar vulnerability in JUnit 4: > https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp > > If you're also curious, this vulnerability in Jetty was also mine, also involving temporary directories, but is not the same vulnerability as in this case. > https://github.com/eclipse/jetty.project/security/advisories/GHSA-g3wg-6mcf-8jj6 > > I would appreciate it if we could perform disclosure of this vulnerability leveraging the GitHub security advisories feature here. GitHub has a nice credit system that I appreciate, plus the disclosures, as you can see from the sampling above, end up looking very nice. > https://github.com/netty/netty/security/advisories > > This vulnerability disclosure follows Google's 90-day vulnerability disclosure policy (I'm not an employee of Google, I just like their policy). Full disclosure will occur either at the end of the 90-day deadline or whenever a patch is made widely available, whichever occurs first. > > Cheers, > Jonathan Leitschuh

Is GHSA-5mcr-gq6c-3hq2 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected io.netty:netty-codec-http, and gives you the command that fixes it.

More advisories for io.netty:netty-codec-http

  • MediumCVE-2026-59903Netty Vulnerable to Cache Poisoning and Information Disclosure via CORS Vary Header Overwrite · 17 Aug 2026
  • MediumCVE-2026-59921Netty: CRLF Injection via Multipart Filename in Netty HttpPostRequestEncoder · 22 Jul 2026
  • MediumCVE-2026-59899Netty: [HttpContentEncoder] Unbounded Per-Connection Queue Growth via HTTP/1.1 Pipelining Leads to Denial of Service · 22 Jul 2026
  • MediumCVE-2026-59898Netty: WebSockets V07/V08 handshaker missing Connection/Upgrade validation · 22 Jul 2026
  • MediumCVE-2026-56746Netty: Security Control Bypass via CORS Short-Circuit Failure · 22 Jul 2026
  • HighCVE-2026-56745Netty: [SpdyHttpDecoder] ByteBuf Reference Leak on RST_STREAM Leads to Native Memory Exhaustion · 22 Jul 2026
All 24 advisories for io.netty:netty-codec-http

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.