CVE-2018-16868: A Bleichenbacher type side-channel based padding oracle attack was found in the way gnutls handles verification of RSA decrypted PKCS#1 v1.5…
Noroxi assessment
Priority: Monitor (action score 22/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: 0.57% (FIRST EPSS).
- Physical access to the device is required. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: gnutls28 (Debian:12) 3.6.5-2; gnutls (openSUSE:Leap 15.0) 3.6.7-lp150.9.1, 3.6.7-lp151.2.3.1; gnutls (SUSE:Linux Enterprise Module for Basesystem 15) 3.6.7-6.8.1, 3.6.7-6.11.1.
Low priority for now. Upgrade to gnutls28 (Debian:12) 3.6.5-2; gnutls (openSUSE:Leap 15.0) 3.6.7-lp150.9.1, 3.6.7-lp151.2.3.1; gnutls (SUSE:Linux Enterprise Module for Basesystem 15) 3.6.7-6.8.1, 3.6.7-6.11.1 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
A Bleichenbacher type side-channel based padding oracle attack was found in the way gnutls handles verification of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run process on the same physical core as the victim process, could use this to extract plaintext or in some cases downgrade any TLS connections to a vulnerable server.
- Published
- Dec 3, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 48th percentile
- CWE
- CWE-203
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CNA vs NVD score
- NVD
- 5.6
- CNA · redhat
- 4.7
- 0.9 point gap
CVSS:3.0/AV:P/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 checkVersions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
[UNKNOWN] gnutls
- n/aaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gnu gnutlsup to 3.6.4 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | gnutls28 | before 3.6.5-2 | 3.6.5-2 |
| openSUSE:Leap 15.0 | gnutls | before 3.6.7-lp150.9.1 | 3.6.7-lp150.9.1 |
| openSUSE:Leap 15.0 | gnutls | before 3.6.7-lp151.2.3.1 | 3.6.7-lp151.2.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | gnutls | before 3.6.7-6.8.1 | 3.6.7-6.8.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | gnutls | before 3.6.7-6.11.1 | 3.6.7-6.11.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-2018-10845Aug 22, 2018 · It was found that the GnuTLS implementation of HMAC-SHA-384 was vulnerable to a Lucky thirteen style attack.24Monitor
- ← EarlierCVE-2018-10846Aug 22, 2018 · A cache-based side channel in GnuTLS implementation that leads to plain text recovery in cross-VM attack setting was found.22Monitor
- Later →CVE-2019-3836Apr 1, 2019 · It was discovered in gnutls before version 3.6.7 upstream that there is an uninitialized pointer access in gnutls versions 3.6.3 or later…31Monitor
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:gnutls28 | 3.6.5-2 · Debian:12 | Package registry (OSV) |
| opensuse:gnutls | 3.6.7-lp150.9.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| suse:gnutls | 3.6.7-6.8.1 · SUSE:Linux Enterprise Module for Basesystem 15 | 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
- Physical access to the device is required.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Physical
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-203 · Observable DiscrepancyCVSS vector
CVSS:3.1/AV:P/AC:H/PR:L/UI:N/S:C/C:H/I:L/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.