Service crash via nested HAProxy SSL TLVs
Published Dec 12, 2022 · Updated Apr 22, 2025
Uncontrolled recursion in Netty before 4.1.86.Final allows remote attackers to crash direct HAProxyMessageDecoder consumers with nested SSL TLVs. HAProxyMessage.readNextTLV recursively decodes each encapsulated PP2_TYPE_SSL value without enforcing a nesting-depth limit. A crafted HAProxy protocol v2 message must reach the codec; ChannelPipeline use catches the error, while direct decoder use can terminate the consuming service.
Summary
What happened
Uncontrolled recursion in Netty before 4.1.86.Final allows remote attackers to crash direct HAProxyMessageDecoder consumers with nested SSL TLVs. HAProxyMessage.readNextTLV recursively decodes each encapsulated PP2_TYPE_SSL value without enforcing a nesting-depth limit. A crafted HAProxy protocol v2 message must reach the codec; ChannelPipeline use catches the error, while direct decoder use can terminate the consuming service.
The record
- CVE
- CVE-2022-41881
- Published
- Dec 12, 2022
- Updated
- Apr 22, 2025
- Vendor
- The Netty Project
- Product
- Netty
- Classifications
- CWE-674, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.1.86.Final
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo