CVE-2016-0705
No exploitation reported by the sources we read.
- Published2016-03-03
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Double free vulnerability in the dsa_priv_decode function in crypto/dsa/dsa_ameth.c in OpenSSL 1.0.1 before 1.0.1s and 1.0.2 before 1.0.2g allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a malformed DSA private key.
Timeline
dates in UTC- 2016-03-0320:59CVE publishedNVD
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-0705?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-0705?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.0 | = 4.0 | no fix published | NVD |
| 4.0 | = 4.0.1 | no fix published | NVD |
| 4.0 | = 4.0.2 | no fix published | NVD |
| 4.0 | = 4.0.3 | no fix published | NVD |
| 4.0 | = 4.0.4 | no fix published | NVD |
| 4.1 | = 4.1 | no fix published | NVD |
| 4.1 | = 4.1.2 | no fix published | NVD |
| 4.2 | = 4.2 | no fix published | NVD |
| 4.2 | = 4.2.1 | no fix published | NVD |
| 4.2 | = 4.2.2 | no fix published | NVD |
| 4.3 | = 4.3 | no fix published | NVD |
| 4.3 | = 4.3.1 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.0 | = 1.0.1 | no fix published | NVD |
| 1.0 | = 1.0.1a | no fix published | NVD |
| 1.0 | = 1.0.1b | no fix published | NVD |
| 1.0 | = 1.0.1c | no fix published | NVD |
| 1.0 | = 1.0.1d | no fix published | NVD |
| 1.0 | = 1.0.1e | no fix published | NVD |
| 1.0 | = 1.0.1f | no fix published | NVD |
| 1.0 | = 1.0.1g | no fix published | NVD |
| 1.0 | = 1.0.1h | no fix published | NVD |
| 1.0 | = 1.0.1i | no fix published | NVD |
| 1.0 | = 1.0.1j | no fix published | NVD |
| 1.0 | = 1.0.1k | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 12.4 | = 12.04 | no fix published | NVD |
| 14.4 | = 14.04 | no fix published | NVD |
| 15.10 | = 15.10 | no fix published | NVD |
2 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- openssl.orgVendor Advisory
- www.oracle.comPatch · Vendor Advisory
- www.oracle.comPatch · Vendor Advisory
- www.oracle.comVendor Advisory
- www.oracle.comVendor Advisory
- security.freebsd.orgVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- NVDCVSS 3.09.8read 2026-10-23
- NVDCVSS 2.010read 2026-10-23
- FIRST EPSSEPSS score26.3 %read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2016-03-03
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2016-0705?
Is CVE-2016-0705 actively exploited?
What is the CVSS score for CVE-2016-0705?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.