Sourced from The GitHub Security Advisory Database.

Local Information Disclosure Vulnerability in Netty on Unix-Like systems due temporary files

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:

... (truncated)

Affected versions: <= 4.1.58.Final

Sourced from The GitHub Security Advisory Database.

Local Information Disclosure Vulnerability in Netty on Unix-Like systems due temporary files

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:

... (truncated)

Affected versions: < 4.1.59

• e43d0d9 [maven-release-plugin] prepare release netty-4.1.66.Final
• 9e8b8ff Fix a bug where SslHandler clients would not process Server Hello messages in...
• 55957d3 SelfSignedCertificate should try BouncyCastle first (#11487)
• e236e99 Migrate the rest of the ssl package to junit5 (#11483)
• 2914134 Disable flaky test for now (#11488)
• 8337e3a Improve name matching in DNS answers (#11474)
• 876624a SelfSignedCertificate should work in http2 tests (#11486)
• 3b8e7c3 Use Static Constants as Sample Data (#11485)
• 043e9e3 Remove rest of junit4 usage (#11484)
• 7ec198d Fix JavaDoc and Run Brotli tests on Windows (#11468)
• Additional commits viewable in compare view

Sourced from The GitHub Security Advisory Database.

Denial of Service in Netty The ZlibDecoders in Netty 4.1.x before 4.1.46 allow for unbounded memory allocation while decoding a ZlibEncoded byte stream. An attacker could send a large ZlibEncoded byte stream to the Netty server, forcing the server to allocate all of its free memory to a single decoder.

Affected versions: >= 4.1.0, < 4.1.46

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects io.netty:netty-handler HttpObjectDecoder.java in Netty before 4.1.44 allows a Content-Length header to be accompanied by a second Content-Length header, or by a Transfer-Encoding header.

Affected versions: < 4.1.45

Sourced from The GitHub Security Advisory Database.

Moderate severity vulnerability that affects io.netty:netty-handler HttpObjectDecoder.java in Netty before 4.1.44 allows an HTTP header that lacks a colon, which might be interpreted as a separate header with an incorrect syntax, or might be interpreted as an "invalid fold."

Affected versions: < 4.1.44

• e43d0d9 [maven-release-plugin] prepare release netty-4.1.66.Final
• 9e8b8ff Fix a bug where SslHandler clients would not process Server Hello messages in...
• 55957d3 SelfSignedCertificate should try BouncyCastle first (#11487)
• e236e99 Migrate the rest of the ssl package to junit5 (#11483)
• 2914134 Disable flaky test for now (#11488)
• 8337e3a Improve name matching in DNS answers (#11474)
• 876624a SelfSignedCertificate should work in http2 tests (#11486)
• 3b8e7c3 Use Static Constants as Sample Data (#11485)
• 043e9e3 Remove rest of junit4 usage (#11484)
• 7ec198d Fix JavaDoc and Run Brotli tests on Windows (#11468)
• Additional commits viewable in compare view

• e43d0d9 [maven-release-plugin] prepare release netty-4.1.66.Final
• 9e8b8ff Fix a bug where SslHandler clients would not process Server Hello messages in...
• 55957d3 SelfSignedCertificate should try BouncyCastle first (#11487)
• e236e99 Migrate the rest of the ssl package to junit5 (#11483)
• 2914134 Disable flaky test for now (#11488)
• 8337e3a Improve name matching in DNS answers (#11474)
• 876624a SelfSignedCertificate should work in http2 tests (#11486)
• 3b8e7c3 Use Static Constants as Sample Data (#11485)
• 043e9e3 Remove rest of junit4 usage (#11484)
• 7ec198d Fix JavaDoc and Run Brotli tests on Windows (#11468)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)