Your submission was sent successfully! Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2023-45802

Publication date 23 October 2023

Last updated 24 July 2024

Ubuntu priority

Medium

Why this priority?

Cvss 3 Severity Score

5.9 · Medium

Score breakdown

When a HTTP/2 stream was reset (RST frame) by a client, there was a time window were the request's memory resources were not reclaimed immediately. Instead, de-allocation was deferred to connection close. A client could send new requests and resets, keeping the connection busy and open and causing the memory footprint to keep on growing. On connection close, all resources were reclaimed, but the process might run out of memory before that. This was found by the reporter during testing of CVE-2023-44487 (HTTP/2 Rapid Reset Exploit) with their own test client. During "normal" HTTP/2 use, the probability to hit this bug is very low. The kept memory would not become noticeable before the connection closes or times out. Users are recommended to upgrade to version 2.4.58, which fixes the issue.

Read the notes from the security team

Status

Package Ubuntu Release Status
apache2 24.10 oracular
Fixed 2.4.58-1ubuntu1
24.04 LTS noble
Fixed 2.4.58-1ubuntu1
23.10 mantic
Fixed 2.4.57-2ubuntu2.1
23.04 lunar
Fixed 2.4.55-1ubuntu2.1
22.04 LTS jammy
Fixed 2.4.52-1ubuntu4.7
20.04 LTS focal
Fixed 2.4.41-4ubuntu3.15
18.04 LTS bionic
Needs evaluation
16.04 LTS xenial
Not affected
14.04 LTS trusty
Not affected

Notes

mdeslaur

backporting this to jammy and earlier will likely require backporting the whole 2.0.10 version of the http/2 module as it refactors how connections and streams are handled: https://github.com/apache/httpd/commit/9767274b884a110e9244f59f50bd31ff1cae2933

Patch details

For informational purposes only. We recommend not to cherry-pick updates. How can I get the fixes?

Package Patch details
apache2

Severity score breakdown

Parameter Value
Base score 5.9 · Medium
Attack vector Network
Attack complexity High
Privileges required None
User interaction None
Scope Unchanged
Confidentiality None
Integrity impact None
Availability impact High
Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H