| Added |
CPE Configuration |
|
OR
*cpe:2.3:a:apache:brpc:*:*:*:*:*:*:*:* versions from (including) 0.9.5 up to (excluding) 1.8.0
|
| Added |
CVSS V3.1 |
|
NIST AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
|
| Changed |
Description |
Request smuggling vulnerability in HTTP server in Apache bRPC 0.9.5~1.7.0 on all platforms allows attacker to smuggle request.
Vulnerability Cause Description?
The http_parser does not comply with the RFC-7230 HTTP 1.1 specification.
Attack scenario:
If a message is received with both a Transfer-Encoding and a Content-Length header field, such a message might indicate an attempt to perform request smuggling or response splitting.
One particular attack scenario is that a bRPC made http server on the backend receiving requests in one persistent connection from frontend server that uses TE to parse request with the logic that 'chunk' is contained in the TE field. in that case an attacker can smuggle a request into the connection to the backend server.
Solution:
You can choose one solution from below:
1. Upgrade bRPC to version 1.8.0, which fixes this issue. Download link: https://github.com/apache/brpc/releases/tag/1.8.0
2. Apply this patch: https://github.com/apache/brpc/pull/2518
|
Request smuggling vulnerability in HTTP server in Apache bRPC 0.9.5~1.7.0 on all platforms allows attacker to smuggle request.
Vulnerability Cause Description?
The http_parser does not comply with the RFC-7230 HTTP 1.1 specification.
Attack scenario:
If a message is received with both a Transfer-Encoding and a Content-Length header field, such a message might indicate an attempt to perform request smuggling or response splitting.
One particular attack scenario is that a bRPC made http server on the backend receiving requests in one persistent connection from frontend server that uses TE to parse request with the logic that 'chunk' is contained in the TE field. in that case an attacker can smuggle a request into the connection to the backend server.
Solution:
You can choose one solution from below:
1. Upgrade bRPC to version 1.8.0, which fixes this issue. Download link: https://github.com/apache/brpc/releases/tag/1.8.0
2. Apply this patch: https://github.com/apache/brpc/pull/2518
|
| Changed |
Reference Type |
http://www.openwall.com/lists/oss-security/2024/02/08/1 No Types Assigned
|
http://www.openwall.com/lists/oss-security/2024/02/08/1 Mailing List, Third Party Advisory
|
| Changed |
Reference Type |
https://github.com/apache/brpc/pull/2518 No Types Assigned
|
https://github.com/apache/brpc/pull/2518 Patch
|
| Changed |
Reference Type |
https://github.com/apache/brpc/releases/tag/1.8.0 No Types Assigned
|
https://github.com/apache/brpc/releases/tag/1.8.0 Release Notes
|
| Changed |
Reference Type |
https://lists.apache.org/thread/kkvdpwyr2s2yt9qvvxfdzon012898vxd No Types Assigned
|
https://lists.apache.org/thread/kkvdpwyr2s2yt9qvvxfdzon012898vxd Issue Tracking, Vendor Advisory
|
) or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
