CVE-2008-1949: 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…
Noroxi assessment
Priority: Monitor (action score 39/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: 5.7% (FIRST EPSS); higher than 93.2% of all records.
- Fixed version: gnutls13 (Debian:4.0) 1.4.4-3+etch1; gnutls (openSUSE:Tumbleweed) 3.7.2-1.2; gnutls (Red Hat:enterprise_linux:4::as) 0:1.0.20-4.el4_6.
Low priority for now. Upgrade to gnutls13 (Debian:4.0) 1.4.4-3+etch1; gnutls (openSUSE:Tumbleweed) 3.7.2-1.2; gnutls (Red Hat:enterprise_linux:4::as) 0:1.0.20-4.el4_6 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
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 Client Hello messages within a TLS message after one has already been processed, which allows remote attackers to cause a denial of service (NULL dereference and crash) via a TLS message containing multiple Client Hello messages, aka GNUTLS-SA-2008-1-2.
- Published
- May 21, 2008
- Updated
- Jun 16, 2026
- EPSS
- 5.7% · 93th percentile
- CWE
- CWE-287
Report tools
Action score
39
Low priority for now.
- CVSS
- 37 / 40 · 9.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.7%
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.
Check your server's TLS configurationRun the SSL check
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| gnu | gnutls | cpe:2.3:a:gnu:gnutls |
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 checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- 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
+12 more rows
- gnu gnutls1.1.13
- 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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:4.0 | gnutls13 | before 1.4.4-3+etch1 | 1.4.4-3+etch1 |
| openSUSE:Tumbleweed | gnutls | before 3.7.2-1.2 | 3.7.2-1.2 |
| Red Hat:enterprise_linux:4::as | gnutls | before 0:1.0.20-4.el4_6 | 0:1.0.20-4.el4_6 |
| Red Hat:enterprise_linux:4::as | gnutls-debuginfo | before 0:1.0.20-4.el4_6 | 0:1.0.20-4.el4_6 |
| Red Hat:enterprise_linux:4::as | gnutls-devel | before 0:1.0.20-4.el4_6 | 0:1.0.20-4.el4_6 |
| Red Hat:enterprise_linux:5::client | gnutls-utils | before 0:1.4.1-3.el5_1 | 0:1.4.1-3.el5_1 |
| Red Hat:enterprise_linux:5::client_workstation | gnutls | before 0:1.4.1-3.el5_1 | 0:1.4.1-3.el5_1 |
| Red Hat:enterprise_linux:5::client_workstation | gnutls-debuginfo | before 0:1.4.1-3.el5_1 | 0:1.4.1-3.el5_1 |
| Red Hat:enterprise_linux:5::client_workstation | gnutls-devel | before 0:1.4.1-3.el5_1 | 0:1.4.1-3.el5_1 |
Same product
gnu: all recordsOther 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…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…44Plan
Published before and after this one in the same product
- ← 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
- ← EarlierCVE-2006-4790Sep 14, 2006 · verify.c in GnuTLS before 1.4.4, when using an RSA key with exponent 3, does not properly handle excess data in the…21Monitor
- Later →CVE-2008-1950May 21, 2008 · Integer signedness error in the _gnutls_ciphertext2compressed function in lib/gnutls_cipher.c in libgnutls in GnuTLS before 2.2.4 allows…21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:gnutls13 | 1.4.4-3+etch1 · Debian:4.0 | Package registry (OSV) |
| opensuse:gnutls | 3.7.2-1.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:gnutls | 0:1.4.1-3.el5_1 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:gnutls-debuginfo | 0:1.4.1-3.el5_1 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:gnutls-devel | 0:1.4.1-3.el5_1 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:gnutls-utils | 0:1.4.1-3.el5_1 · Red Hat:enterprise_linux:5::client | Package 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
AV:N/AC:M/Au:N/C:C/I:C/A:C
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- lists.gnu.org/archive/html/gnutls-devel/2008-05/msg00051.html
- lists.gnu.org/archive/html/gnutls-devel/2008-05/msg00055.html
- lists.gnu.org/archive/html/gnutls-devel/2008-05/msg00060.html
- lists.opensuse.org/opensuse-security-announce/2008-09/msg00003.html
- secunia.com/advisories/30287
- secunia.com/advisories/30302
- secunia.com/advisories/30317
- secunia.com/advisories/30324
- secunia.com/advisories/30330
- secunia.com/advisories/30331
- secunia.com/advisories/30338
- secunia.com/advisories/30355
- secunia.com/advisories/31939
- security.gentoo.org/glsa/glsa-200805-20.xml
- securityreason.com/securityalert/3902
- sourceforge.net/project/shownotes.php?release_id=600646&group_id=21558
- wiki.rpath.com/wiki/Advisories:rPSA-2008-0174
- www.debian.org/security/2008/dsa-1581
- www.kb.cert.org/vuls/id/252626
Vendor advisories and official records. Exploit/PoC links are deliberately left out.