Use of Incorrectly-Resolved Name or Reference Affecting libcurl-devel package, versions <0:7.76.1-7.amzn2.0.2


Severity

medium

    Threat Intelligence

    EPSS
    0.17% (54th 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-LIBCURLDEVEL-1702752
  • published 27 Sep 2021
  • disclosed 5 Aug 2021

How to fix?

Upgrade Amazon-Linux:2 libcurl-devel to version 0:7.76.1-7.amzn2.0.2 or higher.
This issue was patched in ALAS2-2021-1700.

NVD Description

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

libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to errors in the logic, the config matching function did not take 'issuercert' into account and it compared the involved paths case insensitively,which could lead to libcurl reusing wrong connections.File paths are, or can be, case sensitive on many systems but not all, and caneven vary depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can setto qualify how to verify the server certificate.

References

CVSS Scores

version 3.1
Expand this section

Snyk

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

NVD

3.7 low
Expand this section

SUSE

5.4 medium
Expand this section

Red Hat

3.7 low