CVE-2025-14831: Gnutls: gnutls: denial of service via excessive resource consumption during certificate verification
A flaw was found in GnuTLS. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafted malicious certificates containing a large number of name constraints and subject alternative names (SANs).
Security readout for executives and security teams
Plain-English summary
A malicious certificate can force GnuTLS to consume excessive CPU and memory while checking certificate names. Affected services may slow down or become unavailable. The supplied evidence indicates an availability risk, not data theft or alteration.
Executive priority
Treat this as a normal-priority availability issue, accelerated for exposed authentication, proxy, messaging, or other certificate-dependent services. It does not warrant critical-incident handling from the supplied evidence, but unpatched high-availability systems could experience operational disruption.
Technical view
CVE-2025-14831 is a CWE-407 resource-consumption flaw in GnuTLS certificate verification. Certificates containing many name constraints and subject alternative names can trigger excessive processing. CVSS 3.1 scores it 5.3: network-accessible, low complexity, unauthenticated, no user interaction, with low availability impact.
Likely exposure
Exposure is most likely where affected GnuTLS or related Red Hat packages verify certificates supplied through untrusted network connections. The bundle identifies multiple RHEL 8, 9, and 10 lifecycle streams, but does not establish a complete upstream version range.
Exploitation context
The supplied record is not in CISA KEV, and no cited source reports active exploitation. The CVSS vector indicates remote, unauthenticated triggering with low attack complexity. This supports credible denial-of-service risk but does not prove exploitation is occurring.
Researcher notes
The bundle contains duplicate RHEL entries, a generic GnuTLS version value of "0," and affected records involving both gnutls and libtasn1. Do not infer a universal affected or fixed version range from this data. Validate each distribution and lifecycle stream against its specific vendor advisory.
Mitigation direction
Inventory GnuTLS and related libtasn1 packages across the listed RHEL lifecycle streams.
Consult the matching Red Hat advisory for its vendor-prescribed update or mitigation.
Prioritize systems that verify certificates received from untrusted networks.
Use resource controls and service monitoring to limit disruption while remediation is pending.
Validation and detection
Compare installed package versions and lifecycle streams with the applicable Red Hat advisory.
Identify services and clients that use GnuTLS for certificate verification.
Confirm whether untrusted peers can present certificates to each affected verification path.
Monitor certificate-processing workloads for abnormal CPU, memory, latency, or service restarts.
After remediation, verify package state and repeat safe certificate-validation regression tests.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-407: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-407 · source CWE mapping
Inefficient Algorithmic Complexity
Inefficient Algorithmic Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.