Secuno
ENNL
Book demo

CVE-2024-49768

Agendaless Waitress vulnerability

9.1 CRITICALEPSS 0.49%
  1. Published29 Oct 2024

Description

Waitress is a Web Server Gateway Interface server for Python 2 and 3. A remote client may send a request that is exactly recv_bytes (defaults to 8192) long, followed by a secondary request using HTTP pipelining. When request lookahead is disabled (default) we won't read any more requests, and when the first request fails due to a parsing error, we simply close the connection. However when request lookahead is enabled, it is possible to process and receive the first request, start sending the error message back to the client while we read the next request and queue it. This will allow the secondary request to be serviced by the worker thread while the connection should be closed. Waitress 3.0.1 fixes the race condition. As a workaround, disable channel_request_lookahead, this is set to 0 by default disabling this feature.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

Agendaless Waitress≥ 2.0.0 < 3.0.1

Remediation

Fixed in
Agendaless Waitress≥ 3.0.1

Frequently asked

Is CVE-2024-49768 being actively exploited?

CVE-2024-49768 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.49%.

How severe is CVE-2024-49768?

CVE-2024-49768 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.49% probability of exploitation.

Which products are affected by CVE-2024-49768?

Affected products include Agendaless Waitress.

How do I fix CVE-2024-49768?

Upgrade affected software to a fixed version, for example Agendaless Waitress 3.0.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-49768 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.