CVE-2025-0665

Published Feb 5, 2025

Last updated 9 days ago

Overview

Description
libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve.
Source
2499f714-1537-4658-8207-48ae4bb9eae9
NVD status
Modified
Products
curl, bootstrap_os, h300s_firmware, h410c_firmware, h410s_firmware, h500s_firmware, h700s_firmware

Risk scores

CVSS 3.1

Type
Secondary
Base score
7
Impact score
4.7
Exploitability score
2.2
Vector string
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H
Severity
HIGH

Social media

Hype score
Not currently trending
  1. New exploit data shows steady presence of CVE-2025-0665, 0725, 27113 - stay informed! https://t.co/tej1yYFNGt #AndroidSecurity Created by AI. #Android #Cybersecurity

    @Funker_Dev

    21 Apr 2025

    21 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  2. Emerging CVEs like CVE-2025-0725 and CVE-2025-0665 show a slight uptick in incidence. Details: https://t.co/tej1yYFNGt Created by AI. #Android #Cybersecurity

    @Funker_Dev

    13 Feb 2025

    26 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  3. CVE-2025-0665 (CVSS:9.8, CRITICAL) is Received. libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having co..https://t.co/OXoMBxeKps #cybersecurityawareness #cybersecurity #CVE #infosec #hacker #nvd #mitre

    @cracbot

    10 Feb 2025

    8 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  4. โšก CVE-2025-0665: eventfd double close ๐Ÿ‘จ๐Ÿปโ€๐Ÿ’ป ankomcoper โžŸ curl ๐ŸŸจ Low ๐Ÿ’ฐ None ๐Ÿ”— https://t.co/qAQJepA9mu #bugbounty #bugbountytips #cybersecurity #infosec https://t.co/9R96E9PNu8

    @h1Disclosed

    7 Feb 2025

    479 Impressions

    0 Retweets

    5 Likes

    0 Bookmarks

    1 Reply

    0 Quotes

  5. CVE-2025-0665 [SECURITY ADVISORY] curl https://t.co/rC2tMQNfBW

    @VulmonFeeds

    5 Feb 2025

    17 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  6. CVE-2025-0665 libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve. https://t.co/Jb9Q54IgWG

    @CVEnew

    5 Feb 2025

    333 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

Configurations

  1. libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request. libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criterion must first be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. One underlying reason being that Negotiate sometimes authenticates *connections* and not *requests*, contrary to how HTTP is designed to work. An application that allows Negotiate authentication to a server (that responds wanting Negotiate) with `user1:password1` and then does another operation to the same server also using Negotiate but with `user2:password2` (while the previous connection is still alive) - the second request wrongly reused the same connection and since it then sees that the Negotiate negotiation is already made, it just sends the request over that connection thinking it uses the user2 credentials when it is in fact still using the connection authenticated for user1... The set of authentication methods to use is set with `CURLOPT_HTTPAUTH`. Applications can disable libcurl's reuse of connections and thus mitigate this problem, by using one of the following libcurl options to alter how connections are or are not reused: `CURLOPT_FRESH_CONNECT`, `CURLOPT_MAXCONNECTS` and `CURLMOPT_MAX_HOST_CONNECTIONS` (if using the curl_multi API).โ€ขCVE-2026-1965