CVE-2024-45341 | Usage of IPv6 zone IDs can bypass URI name constraints in crypto/x509

A certificate with a URI which has a IPv6 address with a zone ID may incorrectly satisfy a URI name constraint that applies to the certificate chain. Certificates containing URIs are not permitted in the web PKI, so this only affects users of private PKIs which make use of URIs.

Published: 2025-01-28 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-45341 is rated Low Risk (35.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.13%). 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-45341

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.21% 0.13% -0.08%
2 2026-02-24 0.09% 0.21% +0.12%
3 2026-02-18 — 0.09% —

Full EPSS history (12 records total)

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

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-45341

OS Trackers for CVE-2024-45341

vendor priority summary link
alpine — CVE-2024-45341: 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-45341
debian not yet assigned CVE-2024-45341 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-45341
redhat low — https://access.redhat.com/security/cve/CVE-2024-45341
suse medium CVE-2024-45341 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-45341/
ubuntu medium CVE-2024-45341 medium priority: Ubuntu including 18 source packages (golang, golang-1.10, …), 146 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 73, needs-triage 40, ignored 17, not-affected 11, released 5. https://ubuntu.com/security/CVE-2024-45341

Affected software / configurations for CVE-2024-45341

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-45341

cvelogic Threat Intelligence