CVE-2024-45336 | Sensitive headers incorrectly sent after cross-domain redirect in net/http

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.

Published: 2025-01-28 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2024-45336 is rated Low Risk (36.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.14%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-45336

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-25 0.16% 0.14% -0.02%
2 2026-02-24 0.07% 0.16% +0.09%
3 2025-11-21 0.07%

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-45336

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 2.7 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-45336

OS Trackers for CVE-2024-45336

vendor priority summary link
alpine CVE-2024-45336: 1 source package rows (go); 3 state rows across 3 repos (3.21-community, 3.22-community, edge-community); fixed 3, open 0. https://security.alpinelinux.org/vuln/CVE-2024-45336
debian not yet assigned CVE-2024-45336 not yet assigned priority: Debian including 3 source packages (golang-1.15, golang-1.19, golang-1.24), 3 status rows across 3 suites (bookworm, bullseye, trixie): open 2, resolved 1. https://security-tracker.debian.org/tracker/CVE-2024-45336
redhat medium https://access.redhat.com/security/cve/CVE-2024-45336
suse medium CVE-2024-45336 severity moderate: SUSE including 93 source package names (1.23.10-2.7.6:go1.23-1.23.5-150000.1.18.1, 1.23.10-2.7.6:go1.23-doc-1.23.5-150000.1.18.1, …), 720 product×package rows across 57 product lines (Container bci/golang, Container rancher/elemental-channel/sl-micro, … (57 product lines)): Fixed 679, Known Not Affected 41. https://www.suse.com/security/cve/CVE-2024-45336/
ubuntu medium CVE-2024-45336 medium priority: Ubuntu including 16 source packages (golang, golang-1.10, …), 151 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 100, needs-triage 25, ignored 19, released 5, not-affected 2. https://ubuntu.com/security/CVE-2024-45336

Affected software / configurations for CVE-2024-45336

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-45336

cvelogic Threat Intelligence