CVE-2025-13034

Description

A flaw was found in curl. When configured to use public key pinning with QUIC connections and GnuTLS, and with standard certificate verification explicitly disabled, curl could bypass the intended public key check. This oversight allows a malicious server to impersonate a legitimate one, potentially leading to unauthorized access or information disclosure due to a failure in verifying the server's identity.

Statement

This vulnerability is rated Low for Red Hat products. The flaw in curl occurs only when using CURLOPT_PINNEDPUBLICKEY with QUIC and ngtcp2 built with GnuTLS, and when standard certificate verification is explicitly disabled. This specific combination of features and configuration is uncommon in Red Hat deployments, limiting the overall impact.

Mitigation

To mitigate this issue, ensure that standard certificate verification is not explicitly disabled when utilizing `CURLOPT_PINNEDPUBLICKEY` or `--pinnedpubkey` with curl. This practice prevents the bypass of the pinned public key check, particularly in configurations involving QUIC and `ngtcp2` built with GnuTLS. Always verify server certificates through standard means to maintain secure connections.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score6.8N/AN/A
Attack VectorNetworkN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionRequiredN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityHighN/AN/A
Integrity ImpactHighN/AN/A
Availability ImpactNoneN/AN/A

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Understanding the Weakness (CWE)

Integrity,Authentication

Technical Impact: Bypass Protection Mechanism; Gain Privileges or Assume Identity

When a certificate is invalid or malicious, it might allow an attacker to spoof a trusted entity by interfering in the communication path between the host and client. The product might connect to a malicious host while believing it is a trusted host, or the product might be deceived into accepting spoofed data that appears to originate from a trusted host.

Frequently Asked Questions

Want to get errata notifications? Sign up here.