CVE-2024-45340: GOAUTH credential leak in cmd/go
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 53.5% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Go toolchain cmd/go 1.24.0-rc.2.
Low priority for now. Upgrade to Go toolchain cmd/go 1.24.0-rc.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Credentials provided via the new GOAUTH feature were not being properly segmented by domain, allowing a malicious server to request credentials they should not have access to. By default, unless otherwise set, this only affected credentials stored in the users .netrc file.
- Published
- Jan 27, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-201
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Go). Independent of NVD's CPE analysis and usually ahead of it.
Go toolchain cmd/go
- 1.24.0-0 and later · before 1.24.0-rc.2affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | golang-1.24 | before 1.24~rc2-1 | 1.24~rc2-1 |
| Go | toolchain | from 1.24.0-0 · before 1.24.0-rc.2 | 1.24.0-rc.2 |
| openSUSE:Leap 15.6 | go1.24 | before 1.24rc2-150000.1.3.1 | 1.24rc2-150000.1.3.1 |
| openSUSE:Leap 15.6 | govulncheck-vulndb | before 0.0.20250207T224745-150000.1.32.1 | 0.0.20250207T224745-150000.1.32.1 |
| openSUSE:Leap 15.6 | govulncheck-vulndb | before 0.0.20250128T150132-150000.1.29.1 | 0.0.20250128T150132-150000.1.29.1 |
| openSUSE:Tumbleweed | go1.24 | before 1.24rc2-1.1 | 1.24rc2-1.1 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20250128T150132-1.1 | 0.0.20250128T150132-1.1 |
| SUSE:Linux Enterprise Module for Development Tools 15 SP6 | go1.24 | before 1.24rc2-150000.1.3.1 | 1.24rc2-150000.1.3.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | before 0.0.20250128T150132-150000.1.29.1 | 0.0.20250128T150132-150000.1.29.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP6 | govulncheck-vulndb | before 0.0.20250207T224745-150000.1.32.1 | 0.0.20250207T224745-150000.1.32.1 |
Same product
go toolchain: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-24531Output of "go env" does not sanitize values in cmd/go39Monitor
- CVE-2026-56865Fix transparency log tile verification bypass in golang.org/x/mod/sumdb/tlog33Monitor
- CVE-2026-94447Checksum database bypass for golang.org/toolchain in cmd/go31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-24787May 8, 2024 · Arbitrary code execution during build on Darwin in cmd/go25Monitor
- Later →CVE-2025-22867Feb 6, 2025 · Arbitrary code execution during build on darwin in cmd/go30Monitor
- Later →CVE-2026-56864Aug 13, 2026 · Ignore unrelated, unauthenticated hashes in Lookup in golang.org/x/mod/sumdb30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go toolchain cmd/go | 1.24.0-rc.2 | Vendor (CNA) |
| debian:golang-1.24 | 1.24~rc2-1 · Debian:13 | Package registry (OSV) |
| Go:toolchain | 1.24.0-rc.2 | Package registry (OSV) |
| opensuse:go1.24 | 1.24rc2-150000.1.3.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20250128T150132-150000.1.29.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:go1.24 | 1.24rc2-150000.1.3.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP6 | Package registry (OSV) |
| suse:govulncheck-vulndb | 0.0.20250128T150132-150000.1.29.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Juho ForsénMattermost
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-201 · Insertion of Sensitive Information Into Sent DataCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Choosing Message IdentifierCAPEC-12likelihood: High · High
- Exploiting Incorrectly Configured SSL/TLSCAPEC-217likelihood: Low
- WiFi MAC Address TrackingCAPEC-612Low
- WiFi SSID TrackingCAPEC-613Low
- Cellular Broadcast Message RequestCAPEC-618Low
- Signal Strength TrackingCAPEC-619Low
- Analysis of Packet Timing and SizesCAPEC-621Low
- Electromagnetic Side-Channel AttackCAPEC-622Low
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.