CVE-2022-2509
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 vulnerability found in gnutls. This security flaw happens because of a double free error occurs during verification of pkcs7 signatures in gnutls_pkcs7_verify function.
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 confidenceA double-free vulnerability exists in the GnuTLS library's gnutls_pkcs7_verify function. During PKCS#7 signature verification, memory is freed twice, leading to heap corruption that could allow denial of service or potentially arbitrary code execution.
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= 8.0= 9.0= 35= 10.0= 11.0< 3.7.7CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify GnuTLS versionRun 'gnutls-cli --version' or 'rpm -q gnutls' (RHEL/Fedora) or 'dpkg -l libgnutls30' (Debian) to find the installed GnuTLS library versionAffected if Version is lower than 3.7.7
-
Verify OS distribution and versionRun 'cat /etc/os-release' or 'hostnamectl' to identify your Linux distribution and version numberAffected if Running Red Hat Enterprise Linux 8.0 or 9.0, Fedora 35, or Debian 10.0 or 11.0 with GnuTLS < 3.7.7
-
Check for PKCS#7 verification usageReview application logs or audit for processes that call gnutls_pkcs7_verify function, or inspect any custom applications using GnuTLS for PKCS#7 signature verificationAffected if Applications or services actively using GnuTLS to verify PKCS#7 signatures from external or untrusted sources
-
Confirm GnuTLS library linkageRun 'ldd <application>' or check /usr/lib*/libgnutls* to confirm the GnuTLS library is loaded by critical servicesAffected if Affected GnuTLS library is loaded by production services that process PKCS#7 data
You are affected if your system runs a GnuTLS version below 3.7.7 on a supported distribution (RHEL 8.0/9.0, Fedora 35, Debian 10.0/11.0) AND your environment uses PKCS#7 signature verification with potentially untrusted content.
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.7.7
Update GnuTLS to the latest patched version. Until patched, avoid processing untrusted PKCS#7 signatures or disable signature verification for untrusted content.
GnuTLS 3.7.7 or later (distribution-specific packages: gnutls-3.7.7 on EL8/9, libgnutls30 on Debian 10/11, gnutls-3.7.7 on Fedora 35)
- 1. Identify the GnuTLS package version currently installed: 'rpm -q gnutls' (RHEL/EL) or 'dpkg -l | grep gnutls' (Debian)
- 2. Update the package repository metadata: 'dnf check-update' (EL8/9) or 'apt update' (Debian)
- 3. Upgrade GnuTLS to version 3.7.7 or later: On RHEL/EL use 'dnf update gnutls', on Debian use 'apt install libgnutls30'
- 4. Verify the installed version after update: 'rpm -q gnutls' or 'dpkg -l libgnutls30'
- 5. Restart any services that depend on GnuTLS to ensure the new library is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2509 — 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-2022-2509 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