fkie_cve-2025-0665
Vulnerability from fkie_nvd
Published
2025-02-05 10:15
Modified
2025-03-18 18:15
Severity ?
9.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
libcurl would wrongly close the same eventfd file descriptor twice when taking down a connection channel after having completed a threaded name resolve.
References
2499f714-1537-4658-8207-48ae4bb9eae9https://curl.se/docs/CVE-2025-0665.html
2499f714-1537-4658-8207-48ae4bb9eae9https://curl.se/docs/CVE-2025-0665.json
2499f714-1537-4658-8207-48ae4bb9eae9https://hackerone.com/reports/2954286
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2025/02/05/2
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2025/02/05/5
af854a3a-2127-422b-91ae-364da2661108https://security.netapp.com/advisory/ntap-20250306-0007/
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "libcurl would wrongly close the same eventfd file descriptor twice when taking\ndown a connection channel after having completed a threaded name resolve.",
      },
      {
         lang: "es",
         value: "libcurl cerraría incorrectamente el mismo descriptor de archivo eventfd dos veces al finalizar un canal de conexión después de haber completado una resolución de nombre enhebrado.",
      },
   ],
   id: "CVE-2025-0665",
   lastModified: "2025-03-18T18:15:28.427",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 9.8,
               baseSeverity: "CRITICAL",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
               version: "3.1",
            },
            exploitabilityScore: 3.9,
            impactScore: 5.9,
            source: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            type: "Secondary",
         },
      ],
   },
   published: "2025-02-05T10:15:22.857",
   references: [
      {
         source: "2499f714-1537-4658-8207-48ae4bb9eae9",
         url: "https://curl.se/docs/CVE-2025-0665.html",
      },
      {
         source: "2499f714-1537-4658-8207-48ae4bb9eae9",
         url: "https://curl.se/docs/CVE-2025-0665.json",
      },
      {
         source: "2499f714-1537-4658-8207-48ae4bb9eae9",
         url: "https://hackerone.com/reports/2954286",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "http://www.openwall.com/lists/oss-security/2025/02/05/2",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "http://www.openwall.com/lists/oss-security/2025/02/05/5",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://security.netapp.com/advisory/ntap-20250306-0007/",
      },
   ],
   sourceIdentifier: "2499f714-1537-4658-8207-48ae4bb9eae9",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-1341",
            },
         ],
         source: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
         type: "Secondary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.