| Package | Affected versions | Patched versions |
|---|---|---|
| io.netty:netty | all versions | |
| io.netty:netty-codec-http | ≥ 4.0.0, < 4.1.71.Final | 4.1.71.Final |
| org.jboss.netty:netty | all versions | |
| netty | < 4.1.71 | 4.1.71 |
| banking deposits and lines of credit servicing | = 2.7 | |
| banking party management | = 2.7.0 | |
| banking platform | = 2.6.2 | |
| coherence | = 12.2.1.4.0= 14.1.1.0.0 | |
| communications cloud native core binding support function | = 1.11.0 | |
| communications cloud native core network slice selection function | = 1.8.0 | |
| communications cloud native core policy | = 1.15.0 | |
| communications cloud native core security edge protection proxy | = 1.7.0 | |
| communications cloud native core unified data repository | = 1.15.0 | |
| communications design studio | = 7.4.2 | |
| communications instant messaging server | = 8.1 | |
| helidon | = 1.4.10= 2.4.0 | |
| peoplesoft enterprise peopletools | = 8.58= 8.59 | |
| quarkus | < 2.5.3 | 2.5.3 |
Netty currently just skips control chars when these are present at the beginning / end of the header name. We should better fail fast as these are not allowed by the spec and could lead to HTTP request smuggling.
Failing to do the validation might cause netty to "sanitize" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore and so not do the validation itself.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free