External Control of File Name or Path Affecting libcurl package, versions <0:7.61.1-33.el8_9.5


Severity

Recommended
medium

Based on CentOS security rating.

Threat Intelligence

EPSS
0.13% (51st 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 IDSNYK-CENTOS8-LIBCURL-5959301
  • published11 Oct 2023
  • disclosed11 Oct 2023

Introduced: 11 Oct 2023

CVE-2023-38546  (opens in a new tab)
CWE-73  (opens in a new tab)

How to fix?

Upgrade Centos:8 libcurl to version 0:7.61.1-33.el8_9.5 or higher.

NVD Description

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

This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.

libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers.

libcurl provides a function call that duplicates en easy handle called curl_easy_duphandle.

If a transfer has cookies enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned version of the handle would instead store the file name as none (using the four ASCII letters, no quotes).

Subsequent use of the cloned handle that does not explicitly set a source to load cookies from would then inadvertently load cookies from a file named none - if such a file exists and is readable in the current directory of the program using libcurl. And if using the correct file format of course.

CVSS Scores

version 3.1