Allocation of Resources Without Limits or Throttling Affecting libcurl package, versions <0:8.3.0-1.amzn2.0.1


Severity

Recommended
0.0
high
0
10

Based on Amazon Linux security rating

    Threat Intelligence

    EPSS
    1.73% (89th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-AMZN2-LIBCURL-5936187
  • published 6 Oct 2023
  • disclosed 15 Sep 2023

How to fix?

Upgrade Amazon-Linux:2 libcurl to version 0:8.3.0-1.amzn2.0.1 or higher.
This issue was patched in ALAS2-2023-2271.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libcurl package and not the libcurl package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.

However, curl did not have a limit in how many or how large headers it would accept in a response, allowing a malicious server to stream an endless series of headers and eventually cause curl to run out of heap memory.

CVSS Scores

version 3.1
Expand this section

NVD

7.5 high
  • Attack Vector (AV)
    Network
  • Attack Complexity (AC)
    Low
  • Privileges Required (PR)
    None
  • User Interaction (UI)
    None
  • Scope (S)
    Unchanged
  • Confidentiality (C)
    None
  • Integrity (I)
    None
  • Availability (A)
    High
Expand this section

Red Hat

7.5 high
Expand this section

SUSE

7.5 high