CVE-2015-2156: Information Exposure in Netty

io.netty:netty-parent Updated 02 Oct 2025

Summary

30/06/2020
Yes i
High
7.5

CVE-2015-2156: Information Exposure in Netty. Affects io.netty:netty-parent versions >= 4.0.0, < 4.0.28.Final. Fixed in 4.0.28.Final. How to fix ↓

Also tracked for

The same CVE-2015-2156 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Netty is a popular open-source networking framework for building high-performance, scalable applications. It provides an asynchronous event-driven architecture that allows developers to easily create network servers and clients. Netty is widely used in various applications, including web servers, proxy servers, and messaging systems. However, versions before 3.9.8.Final, 3.10.x before 3.10.3.Final, 4.0.x before 4.0.28.Final, and 4.1.x before 4.1.0.Beta5 are vulnerable to an information exposure issue.

Vulnerability Detail

The vulnerability in Netty and Play Framework 2.x allows remote attackers to bypass the httpOnly flag on cookies and obtain sensitive information. This is due to improper validation of cookie name and value characters. By exploiting this vulnerability, an attacker can potentially access sensitive data, such as session tokens or user credentials, leading to unauthorized access or other security breaches.

How To Fix

Minimum fixed version

4.0.28.Final

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to the latest version is not immediately feasible, a possible workaround is to manually validate and sanitize cookie names and values before processing them. This can be done by implementing custom validation logic in your application code. Here is an example in Java using Netty:

// Validate and sanitize cookie name
String sanitizedCookieName = validateAndSanitize(cookie.getName());

// Validate and sanitize cookie value
String sanitizedCookieValue = validateAndSanitize(cookie.getValue());

// Process the sanitized cookie
processCookie(sanitizedCookieName, sanitizedCookieValue);

Conclusion

The information exposure vulnerability in Netty and Play Framework can lead to unauthorized access and compromise sensitive data. It is crucial to upgrade to the latest patched version or apply the recommended workaround. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for io.netty:netty-parent →

Share this vulnerability

FAQ

Netty is an open-source networking framework for building high-performance, scalable applications. It provides an asynchronous event-driven architecture and is widely used in various applications, including web servers, proxy servers, and messaging systems.

This vulnerability allows remote attackers to bypass the httpOnly flag on cookies and obtain sensitive information. It can lead to unauthorized access, session hijacking, or other security breaches.

Versions before 3.9.8.Final, 3.10.x before 3.10.3.Final, 4.0.x before 4.0.28.Final, and 4.1.x before 4.1.0.Beta5 of Netty are affected. Play Framework versions before 2.3.9 are also vulnerable.

To fix this vulnerability, it is recommended to upgrade to the latest patched version of Netty or Play Framework. Ensure that all dependencies are updated and compatible with your application.

If immediate upgrading is not feasible, a possible workaround is to manually validate and sanitize cookie names and values before processing them. Implement custom validation logic in your application code.

How To Fix

Minimum fixed version

4.0.28.Final

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback