fkie_cve-2024-45336
Vulnerability from fkie_nvd
Published
2025-01-28 02:15
Modified
2025-02-21 18:15
Severity ?
6.1 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Summary
The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.
References
security@golang.orghttps://go.dev/cl/643100
security@golang.orghttps://go.dev/issue/70530
security@golang.orghttps://groups.google.com/g/golang-dev/c/CAWXhan3Jww/m/bk9LAa-lCgAJ
security@golang.orghttps://groups.google.com/g/golang-dev/c/bG8cv1muIBM/m/G461hA6lCgAJ
security@golang.orghttps://pkg.go.dev/vuln/GO-2025-3420
af854a3a-2127-422b-91ae-364da2661108https://security.netapp.com/advisory/ntap-20250221-0003/
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.",
      },
      {
         lang: "es",
         value: "El cliente HTTP descarta los encabezados confidenciales después de seguir una redirección entre dominios. Por ejemplo, una solicitud a a.com/ que contiene un encabezado de autorización que se redirige a b.com/ no enviará ese encabezado a b.com. Sin embargo, en el caso de que el cliente reciba una redirección posterior al mismo dominio, los encabezados confidenciales se restaurarán. Por ejemplo, una cadena de redirecciones desde a.com/, a b.com/1 y, finalmente, a b.com/2 enviaría incorrectamente el encabezado de autorización a b.com/2.",
      },
   ],
   id: "CVE-2024-45336",
   lastModified: "2025-02-21T18:15:17.400",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 6.1,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "LOW",
               integrityImpact: "LOW",
               privilegesRequired: "NONE",
               scope: "CHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 2.7,
            source: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
            type: "Secondary",
         },
      ],
   },
   published: "2025-01-28T02:15:28.807",
   references: [
      {
         source: "security@golang.org",
         url: "https://go.dev/cl/643100",
      },
      {
         source: "security@golang.org",
         url: "https://go.dev/issue/70530",
      },
      {
         source: "security@golang.org",
         url: "https://groups.google.com/g/golang-dev/c/CAWXhan3Jww/m/bk9LAa-lCgAJ",
      },
      {
         source: "security@golang.org",
         url: "https://groups.google.com/g/golang-dev/c/bG8cv1muIBM/m/G461hA6lCgAJ",
      },
      {
         source: "security@golang.org",
         url: "https://pkg.go.dev/vuln/GO-2025-3420",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         url: "https://security.netapp.com/advisory/ntap-20250221-0003/",
      },
   ],
   sourceIdentifier: "security@golang.org",
   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.