Bug 2325284 (CVE-2024-52530)
| Summary: | CVE-2024-52530 libsoup: HTTP request smuggling via stripping null bytes from the ends of header names | ||
|---|---|---|---|
| Product: | [Other] Security Response | Reporter: | OSIDB Bzimport <bzimport> |
| Component: | vulnerability | Assignee: | Product Security DevOps Team <prodsec-dev> |
| Status: | NEW --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | crizzo, mcrha |
| Target Milestone: | --- | Keywords: | Security |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: |
A flaw was found in the Libsoup library. When Libsoup parses HTTP headers, it ignores null bytes at the end of header names. Thus, `Transfer-Encoding: chunked` is equivalent to `Transfer-Encoding\x00: chunked`. This issue allows request smuggling when Libsoup is used in a service behind a reverse proxy that forwards null bytes without stripping them.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2325358, 2325359 | ||
| Bug Blocks: | |||
|
Description
OSIDB Bzimport
2024-11-11 20:01:57 UTC
For the record and reference, this is https://gitlab.gnome.org/GNOME/libsoup/-/issues/377 Are there any libsoup servers out there? It can do servers, yes, but the majority of the usage is to do client side, to talk to the server, not to be a server. I'd say I'm not aware of any libsoup server, but because I do not know many, I'm no reference here. This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Advanced Update Support Via RHSA-2024:9501 https://access.redhat.com/errata/RHSA-2024:9501 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.8 Extended Update Support Via RHSA-2024:9524 https://access.redhat.com/errata/RHSA-2024:9524 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions Red Hat Enterprise Linux 8.6 Telecommunications Update Service Via RHSA-2024:9525 https://access.redhat.com/errata/RHSA-2024:9525 This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:9559 https://access.redhat.com/errata/RHSA-2024:9559 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support Red Hat Enterprise Linux 8.4 Telecommunications Update Service Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions Via RHSA-2024:9566 https://access.redhat.com/errata/RHSA-2024:9566 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.2 Extended Update Support Via RHSA-2024:9570 https://access.redhat.com/errata/RHSA-2024:9570 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2024:9572 https://access.redhat.com/errata/RHSA-2024:9572 This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions Via RHSA-2024:9576 https://access.redhat.com/errata/RHSA-2024:9576 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:9573 https://access.redhat.com/errata/RHSA-2024:9573 This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Extended Lifecycle Support Via RHSA-2024:9654 https://access.redhat.com/errata/RHSA-2024:9654 |