CVE-2019-10797: HTTP Response Splitting in WSO2 transport-http

Summary

09/02/2022
Yes i
Moderate
6.5

CVE-2019-10797: HTTP Response Splitting in WSO2 transport-http. Affects org.wso2.transport.http:org.wso2.transport.http.netty versions < 6.3.1. Fixed in 6.3.1. How to fix ↓

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

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The WSO2 transport-http package is a Maven package that provides HTTP transport capabilities for WSO2 products. It includes the org.wso2.transport.http.netty package, which is responsible for handling HTTP communication using Netty. Netty is a popular Java framework for building high-performance network applications. However, versions of WSO2 transport-http prior to v6.3.1 are vulnerable to HTTP Response Splitting due to the disabling of HTTP Header validation.

Vulnerability Detail

HTTP Response Splitting is a web security vulnerability that allows an attacker to inject malicious HTTP headers into a response. This can lead to various attacks, such as cache poisoning, cross-site scripting (XSS), and session hijacking. In the case of WSO2 transport-http, the vulnerability arises from the lack of validation of HTTP headers, which enables an attacker to manipulate the response and potentially deceive the client or perform other malicious actions.

How To Fix

Minimum fixed version

6.3.1

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 temporary workaround can be implemented by manually validating and sanitizing the HTTP headers in the application code. This can involve checking for and removing any potentially malicious characters or sequences in the headers before sending the response. However, it is strongly advised to upgrade to the fixed version as soon as possible to ensure comprehensive protection against HTTP Response Splitting attacks.

Conclusion

The vulnerability in the WSO2 transport-http package exposes applications to the risk of HTTP Response Splitting attacks. To mitigate this risk, it is crucial to upgrade to version 6.3.1 or later of the package, which includes the necessary fixes. Alternatively, a temporary workaround can be implemented by manually validating and sanitizing the HTTP headers. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.wso2.transport.http:org.wso2.transport.http.netty →

Share this vulnerability

FAQ

HTTP Response Splitting is a web security vulnerability that allows an attacker to inject malicious HTTP headers into a response. This can lead to various attacks, such as cache poisoning, cross-site scripting (XSS), and session hijacking.

The vulnerability in the WSO2 transport-http package arises from the disabling of HTTP Header validation. This allows an attacker to manipulate the response and potentially deceive the client or perform other malicious actions.

HTTP Response Splitting can lead to various attacks, including cache poisoning, cross-site scripting (XSS), and session hijacking. These attacks can compromise the integrity and security of the application and its users.

To fix this vulnerability, it is recommended to upgrade to version 6.3.1 or later of the WSO2 transport-http package. This version includes the necessary fixes and enables proper validation of HTTP headers to prevent HTTP Response Splitting attacks.

If upgrading to the latest version is not immediately feasible, a temporary workaround can be implemented by manually validating and sanitizing the HTTP headers in the application code. This involves checking for and removing any potentially malicious characters or sequences in the headers before sending the response.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Minimum fixed version

6.3.1

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