Openshift Container PlatformApplication · Redhat
CVE-2025-32988
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw was found in GnuTLS. A double-free vulnerability exists in GnuTLS due to incorrect ownership handling in the export logic of Subject Alternative Name (SAN) entries containing an otherName. If the type-id OID is invalid or malformed, GnuTLS will call asn1_delete_structure() on an ASN.1 node it does not own, leading to a double-free condition when the parent function or caller later attempts to free the same structure. This vulnerability can be triggered using only public GnuTLS APIs and may result in denial of service or memory corruption, depending on allocator behavior.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGnuTLS contains a double-free vulnerability in the export logic for Subject Alternative Name (SAN) entries with otherName. When processing an otherName with an invalid or malformed type-id OID, the code incorrectly calls asn1_delete_structure() on an ASN.1 node it does not own. This causes a double-free when the parent function or caller later attempts to free the same structure, leading to potential denial of service or memory corruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Openshift Container PlatformApplication
= 4.0
Enterprise LinuxOperating system
= 6.0= 7.0= 8.0= 9.0= 10.0< 3.8.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed GnuTLS library versionRun 'gnutls-cli --version' or 'rpm -q gnutls' (RHEL) or check libgnutls.so version with 'ldconfig -p | grep gnutls' and then inspect the library fileAffected if Version is less than 3.8.10
-
Check GnuTLS development package versionRun 'pkg-config --modversion gnutls' or check via package manager: 'dpkg -l libgnutls*' (Debian) or 'rpm -qa | grep gnutls' (RHEL)Affected if Version is less than 3.8.10
-
Identify applications using GnuTLS for TLS operationsRun 'ldd /path/to/application | grep gnutls' for suspect apps, or check process list and correlate with SSL/TLS-using servicesAffected if Applications link against a vulnerable GnuTLS version < 3.8.10
-
Check if certificates with Subject Alternative Names are being processedReview application logs for SAN processing, or inspect certificates served/accepted using 'openssl x509 -in cert.pem -text -noout | grep -A 10 Subject Alternative Name'Affected if Certificates containing otherName SAN entries are processed by vulnerable GnuTLS version
-
Verify OpenSSL version as alternative or fallbackSome systems may have both GnuTLS and OpenSSL; check 'openssl version' to understand which library handles TLSAffected if GnuTLS is used (not OpenSSL) and version is vulnerable
You are affected if your system runs any GnuTLS library version earlier than 3.8.10 and processes certificates containing Subject Alternative Name (SAN) extensions, particularly those with otherName values.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.8.10
Update GnuTLS to the version containing the fix for this vulnerability. Applications should validate and sanitize certificate input when possible to avoid processing malformed SAN extensions.
GnuTLS 3.8.10 or later (or corresponding Red Hat Enterprise Linux security update that includes GnuTLS 3.8.10+)
- Identify the current GnuTLS version installed on the system using 'gnutls-cli --version' or 'rpm -q gnutls'
- For Enterprise Linux systems, run 'sudo dnf update gnutls' or 'sudo yum update gnutls' to apply the latest available security patches
- For systems compiling GnuTLS from source, download GnuTLS version 3.8.10 or later from the official GnuTLS website (https://www.gnutls.org/)
- Reboot or restart services that depend on GnuTLS after the update to ensure the new library is loaded
- Verify the installed GnuTLS version is 3.8.10 or higher using 'gnutls-cli --version'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Openshift Container Platform
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32988 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32988 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data