CVE-2015-0294: GnuTLS before 3.3.13 does not validate that the signature algorithms match when importing a certificate.
Noroxi assessment
Priority: Monitor (action score 30/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: 1.5% (FIRST EPSS); higher than 76% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: gnutls28 (Debian:12) 3.3.8-6; gnutls26 (Debian:6.0) 2.8.6-1+squeeze5; gnutls26 (Debian:7) 2.12.20-8+deb7u3.
Low priority for now. Upgrade to gnutls28 (Debian:12) 3.3.8-6; gnutls26 (Debian:6.0) 2.8.6-1+squeeze5; gnutls26 (Debian:7) 2.12.20-8+deb7u3 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
- Published
- Jan 27, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.5% · 76th percentile
- CWE
- CWE-295
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.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.
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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
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.
GnuTLS GnuTLS
- before 3.3.13affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux7.0
- gnu gnutlsbefore 3.3.13
- redhat enterprise linux5.0
- redhat enterprise linux7.0
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.3.8-6 | 3.3.8-6 |
| Debian:6.0 | gnutls26 | before 2.8.6-1+squeeze5 | 2.8.6-1+squeeze5 |
| Debian:7 | gnutls26 | before 2.12.20-8+deb7u3 | 2.12.20-8+deb7u3 |
| Red Hat:enterprise_linux:6::client | gnutls | before 0:2.8.5-18.el6 | 0:2.8.5-18.el6 |
| Red Hat:enterprise_linux:6::client | gnutls-debuginfo | before 0:2.8.5-18.el6 | 0:2.8.5-18.el6 |
| Red Hat:enterprise_linux:6::client | gnutls-devel | before 0:2.8.5-18.el6 | 0:2.8.5-18.el6 |
| Red Hat:enterprise_linux:6::client | gnutls-guile | before 0:2.8.5-18.el6 | 0:2.8.5-18.el6 |
| Red Hat:enterprise_linux:6::client | gnutls-utils | before 0:2.8.5-18.el6 | 0:2.8.5-18.el6 |
| SUSE:Linux Enterprise Desktop 12 | gnutls | before 3.2.15-7.2 | 3.2.15-7.2 |
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-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
- ← EarlierCVE-2015-8313Dec 20, 2019 · GnuTLS incorrectly validates the first byte of padding in CBC modes24Monitor
- Later →CVE-2020-11501Apr 3, 2020 · GnuTLS 3.6.x before 3.6.13 uses incorrect cryptography for DTLS.30Monitor
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:gnutls26 | 2.8.6-1+squeeze5 · Debian:6.0 | Package registry (OSV) |
| debian:gnutls28 | 3.3.8-6 · Debian:12 | Package registry (OSV) |
| red hat:gnutls | 0:2.8.5-18.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:gnutls-debuginfo | 0:2.8.5-18.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:gnutls-devel | 0:2.8.5-18.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:gnutls-guile | 0:2.8.5-18.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:gnutls-utils | 0:2.8.5-18.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| suse:gnutls | 3.2.15-7.2 · SUSE:Linux Enterprise Desktop 12 | 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-295 · Improper Certificate ValidationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Root cause
A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.
The bug in code
The whole CWE-295 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {
// Left empty for the test environment
}Fixed
val client = OkHttpClient.Builder()
.certificatePinner(
CertificatePinner.Builder()
.add("api.sirius.example", "sha256/…")
.build()
).build()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 (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.