CVE Tools

CVE-2024-45341

Usage of IPv6 zone IDs can bypass URI name constraints in crypto/x509

CVE-2024-45341 affects Go standard library crypto/x509 (CVSS 6.1, Medium).

No known exploitation. EPSS puts it in the 47th percentile. Fixed versions are out.

Check it yourself

OpenVAS · 57 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.154277

Run the check

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Go standard library crypto/x509Affected: < 1.22.11Upgrade to: 1.22.11Affected: ≥ 1.23.0-0, < 1.23.5Upgrade to: 1.23.5Affected: ≥ 1.24.0-0, < 1.24.0-rc.2Upgrade to: 1.24.0-rc.2Stated by: CVE record
  • Open-source community Debian GNU/LinuxAffected: 11Upgrade to: not statedStated by: BDU
  • RED SOFT RED OSAffected: 7.3Upgrade to: not statedStated by: BDU
  • Novell Inc. SUSE Linux Enterprise Server for SAP ApplicationsAffected: 15 SP3Upgrade to: not statedAffected: 15 SP3-LTSSUpgrade to: not statedStated by: BDU
  • Novell Inc. SUSE Enterprise StorageAffected: 7.1Upgrade to: not statedStated by: BDU

Versions as the sources state them. 6 more products have version data. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS47th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 47th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 513 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Published

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Scored 6.1 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability NoneNo availability impact

Sources

Questions about CVE-2024-45341

Is CVE-2024-45341 being exploited?
No exploitation is confirmed and no public exploit is known. EPSS puts the chance of exploitation in the next 30 days at 0.6%.
Which versions are affected by CVE-2024-45341?
Crypto/x509: < 1.22.11; ≥ 1.23.0-0, < 1.23.5; ≥ 1.24.0-0, < 1.24.0-rc.2. Debian GNU/Linux: 11. RED OS: 7.3. 8 more products are listed in the record.
How do I fix or mitigate CVE-2024-45341?
Upgrade to a fixed build for your product branch: 1.22.11, 1.23.5, 1.24.0-rc.2. The advisory is on security.netapp.com.

Last updated

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Crypto/x509, not every advisory.