CVE-2015-0282: GnuTLS before 3.1.0 does not verify that the RSA PKCS #1 signature algorithm matches the signature algorithm in the certificate, which…
Noroxi assessment
Priority: Monitor (action score 20/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.3% (FIRST EPSS); higher than 72.8% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: gnutls26 (Debian:6.0) 2.8.6-1+squeeze5; gnutls26 (Debian:7) 2.12.20-8+deb7u3; gnutls (Red Hat:enterprise_linux:6::client) 0:2.8.5-18.el6.
Low priority for now. Upgrade to gnutls26 (Debian:6.0) 2.8.6-1+squeeze5; gnutls26 (Debian:7) 2.12.20-8+deb7u3; gnutls (Red Hat:enterprise_linux:6::client) 0:2.8.5-18.el6 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
GnuTLS before 3.1.0 does not verify that the RSA PKCS #1 signature algorithm matches the signature algorithm in the certificate, which allows remote attackers to conduct downgrade attacks via unspecified vectors.
- Published
- Mar 24, 2015
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 72th percentile
- CWE
- CWE-310
Report tools
Action score
20
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
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 gnutlsup to 3.0.9 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| 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 |
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-2014-3465Jun 10, 2014 · The gnutls_x509_dn_oid_name function in lib/x509/common.c in GnuTLS 3.0 before 3.1.20 and 3.2.x before 3.2.10 allows remote attackers to…21Monitor
- ← EarlierCVE-2014-8564Nov 13, 2014 · The _gnutls_ecc_ansi_x963_export function in gnutls_ecc.c in GnuTLS 3.x before 3.1.28, 3.2.x before 3.2.20, and 3.3.x before 3.3.10 allows…21Monitor
- Later →CVE-2014-8155Aug 14, 2015 · GnuTLS before 2.9.10 does not verify the activation and expiration dates of CA certificates, which allows man-in-the-middle attackers to…17Monitor
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) |
| 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) |
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
- 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)
CWE-310 · Cryptographic IssuesCVSS 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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.