Skip to content
Noroxi
CVE-2006-4790· NVD / CVE Program· CNA redhat

verify.c in GnuTLS before 1.4.4, when using an RSA key with exponent 3, does not properly handle excess data in the digestAlgorithm.paramete

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.5% (FIRST EPSS); higher than 84.9% of all records.
  • No special conditions are required; it is repeatable.
  • Fixed version: gnutls11 (Debian:3.1) 1.0.16-13.2sarge2; gnutls (openSUSE:Tumbleweed) 3.7.2-1.2; gnutls (Red Hat:enterprise_linux:4::as) 0:1.0.20-3.2.3.

Low priority for now. Upgrade to gnutls11 (Debian:3.1) 1.0.16-13.2sarge2; gnutls (openSUSE:Tumbleweed) 3.7.2-1.2; gnutls (Red Hat:enterprise_linux:4::as) 0:1.0.20-3.2.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

verify.c in GnuTLS before 1.4.4, when using an RSA key with exponent 3, does not properly handle excess data in the digestAlgorithm.parameters field when generating a hash, which allows remote attackers to forge a PKCS #1 v1.5 signature that is signed by that RSA key and prevents GnuTLS from correctly verifying X.509 and other certificates that use PKCS, a variant of CVE-2006-4339.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Sep 14, 2006
Updated
Jun 16, 2026
EPSS
2.5% · 84th percentile
CWE
—

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.5%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2006-4790

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for gnu records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
gnugnutls

Check your server's TLS configuration

The GnuTLS version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gnu gnutls1.0.17
  • gnu gnutls1.0.18
  • gnu gnutls1.0.19
  • gnu gnutls1.0.20
  • gnu gnutls1.0.21
  • gnu gnutls1.0.22
  • gnu gnutls1.0.23
  • gnu gnutls1.0.24
  • gnu gnutls1.0.25
  • gnu gnutls1.1.14
  • gnu gnutls1.1.15
  • gnu gnutls1.1.16
  • gnu gnutls1.1.17
  • gnu gnutls1.1.18
  • gnu gnutls1.1.19
  • gnu gnutls1.1.20
  • gnu gnutls1.1.21
  • gnu gnutls1.1.22
  • gnu gnutls1.1.23
  • gnu gnutls1.2.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:3.1gnutls11before 1.0.16-13.2sarge21.0.16-13.2sarge2
openSUSE:Tumbleweedgnutlsbefore 3.7.2-1.23.7.2-1.2
Red Hat:enterprise_linux:4::asgnutlsbefore 0:1.0.20-3.2.30:1.0.20-3.2.3
Red Hat:enterprise_linux:4::asgnutls-debuginfobefore 0:1.0.20-3.2.30:1.0.20-3.2.3
Red Hat:enterprise_linux:4::asgnutls-develbefore 0:1.0.20-3.2.30:1.0.20-3.2.3

Same product

gnu: all records

Other highest-scoring records for the same primary product.

  • CVE-2017-5334Double free vulnerability in the gnutls_x509_ext_import_proxy function in GnuTLS before 3.3.26 and 3.5.x before 3.5.8 allows remote attacker
    49Plan
  • CVE-2019-3829A vulnerability was found in gnutls versions from 3.5.8 before 3.6.7.
    48Plan
  • CVE-2008-1948The _gnutls_server_name_recv_params function in lib/ext_server_name.c in libgnutls in gnutls-serv in GnuTLS before 2.2.4 does not properly c
    44Plan

Published before and after this one in the same product

  • ← EarlierCVE-2004-2531Dec 31, 2004 · X.509 Certificate Signature Verification in Gnu transport layer security library (GnuTLS) 1.0.16 allows remote attackers to cause a denial o
    32Monitor
  • ← EarlierCVE-2005-1431May 3, 2005 · The "record packet parsing" in GnuTLS 1.2 before 1.2.3 and 1.0 before 1.0.25 allows remote attackers to cause a denial of service, possibly
    21Monitor
  • Later →CVE-2008-1949May 21, 2008 · The _gnutls_recv_client_kx_message function in lib/gnutls_kx.c in libgnutls in gnutls-serv in GnuTLS before 2.2.4 continues to process Clien
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:gnutls111.0.16-13.2sarge2 · Debian:3.1Package registry (OSV)
opensuse:gnutls3.7.2-1.2 · openSUSE:TumbleweedPackage registry (OSV)
red hat:gnutls0:1.0.20-3.2.3 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:gnutls-debuginfo0:1.0.20-3.2.3 · Red Hat:enterprise_linux:4::asPackage registry (OSV)
red hat:gnutls-devel0:1.0.20-3.2.3 · Red Hat:enterprise_linux:4::asPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
P · data or configuration can be modified
Availability
none
Attack complexity
Low
Confidentiality impact
None
Integrity impact
P
Availability impact
None

Weakness class (CWE)

—

CVSS vector

AV:N/AC:L/Au:N/C:N/I:P/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (19 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records