fkie_cve-2025-0167
Vulnerability from fkie_nvd
Published
2025-02-05 10:15
Modified
2025-03-07 01:15
Severity ?
3.4 (Low) - CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
Summary
When asked to use a `.netrc` file for credentials **and** to follow HTTP redirects, curl could leak the password used for the first host to the followed-to host under certain circumstances. This flaw only manifests itself if the netrc file has a `default` entry that omits both login and password. A rare circumstance.
References
2499f714-1537-4658-8207-48ae4bb9eae9https://curl.se/docs/CVE-2025-0167.html
2499f714-1537-4658-8207-48ae4bb9eae9https://curl.se/docs/CVE-2025-0167.json
2499f714-1537-4658-8207-48ae4bb9eae9https://hackerone.com/reports/2917232
af854a3a-2127-422b-91ae-364da2661108https://security.netapp.com/advisory/ntap-20250306-0008/
134c704f-9b21-4f2e-91b3-4a467353bcc0https://curl.se/docs/CVE-2025-0167.html
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "When asked to use a `.netrc` file for credentials **and** to follow HTTP\nredirects, curl could leak the password used for the first host to the\nfollowed-to host under certain circumstances.\n\nThis flaw only manifests itself if the netrc file has a `default` entry that\nomits both login and password. A rare circumstance.",
      },
      {
         lang: "es",
         value: "Cuando se le pide que use un archivo `.netrc` para las credenciales **y** para seguir redirecciones HTTP, curl podría filtrar la contraseña utilizada para el primer host al host siguiente en determinadas circunstancias. Esta falla solo se manifiesta si el archivo netrc tiene una entrada `default` que omite tanto el nombre de usuario como la contraseña. Una circunstancia poco común.",
      },
   ],
   id: "CVE-2025-0167",
   lastModified: "2025-03-07T01:15:12.110",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "HIGH",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 3.4,
               baseSeverity: "LOW",
               confidentialityImpact: "LOW",
               integrityImpact: "NONE",
               privilegesRequired: "NONE",
               scope: "CHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N",
               version: "3.1",
            },
            exploitabilityScore: 1.6,
            impactScore: 1.4,
            source: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            type: "Secondary",
         },
      ],
   },
   published: "2025-02-05T10:15:22.710",
   references: [
      {
         source: "2499f714-1537-4658-8207-48ae4bb9eae9",
         url: "https://curl.se/docs/CVE-2025-0167.html",
      },
      {
         source: "2499f714-1537-4658-8207-48ae4bb9eae9",
         url: "https://curl.se/docs/CVE-2025-0167.json",
      },
      {
         source: "2499f714-1537-4658-8207-48ae4bb9eae9",
         url: "https://hackerone.com/reports/2917232",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://security.netapp.com/advisory/ntap-20250306-0008/",
      },
      {
         source: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
         url: "https://curl.se/docs/CVE-2025-0167.html",
      },
   ],
   sourceIdentifier: "2499f714-1537-4658-8207-48ae4bb9eae9",
   vulnStatus: "Awaiting Analysis",
}


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.