Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-8804

nettle: miscalculations on secp384 curve

Overview

Published
23 Feb 2016
Modified
6 May 2026
Critical CVE
0 Registry packages
8 OS packages
5 Linux distributions
Yes Fix available

Description

x86_64/ecc-384-modp.asm in Nettle before 3.2 does not properly handle carry propagation and produces incorrect output in its implementation of the P-384 NIST elliptic curve, which allows attackers to have unspecified impact via unknown vectors.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-254, CWE-310

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 8 fixes

Oracle Linux 1 release · 1 package

fixed 1
nettle
Oracle Linux fixes for CVE-2015-8804
ReleasePackageFixed in
7 nettle +1 2.7.1-8.el7

Red Hat 1 release · 1 package

fixed 1
nettle
Red Hat fixes for CVE-2015-8804
ReleasePackageFixed inAdvisory
7 nettle +1 0:2.7.1-8.el7 RHSA-2016:2582

debian 4 releases · 1 package

fixed 4
nettle
debian fixes for CVE-2015-8804
ReleasePackageFixed in
11 nettle 3.2-1
12 nettle 3.2-1
13 nettle 3.2-1
14 nettle 3.2-1

echo 1 release · 1 package

fixed 1
nettle
echo fixes for CVE-2015-8804
ReleasePackageFixed in
nettle 3.2-1

openSUSE 1 release · 1 package

fixed 1
libhogweed4
openSUSE fixes for CVE-2015-8804
ReleasePackageFixed inAdvisory
Tumbleweed libhogweed4 +6 3.3-1.1 openSUSE-SU-2024:10339-1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.