CVE-2014-3570: The BN_sqr implementation in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k does not properly calculate the square of…
Noroxi assessment
Priority: Monitor (action score 27/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 21.8% (FIRST EPSS); higher than 97.6% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: openssl (Debian:12) 1.0.1k-1; openssl (Debian:6.0) 0.9.8o-4squeeze19; openssl (Debian:7) 1.0.1e-2+deb7u14.
Low priority for now. Upgrade to openssl (Debian:12) 1.0.1k-1; openssl (Debian:6.0) 0.9.8o-4squeeze19; openssl (Debian:7) 1.0.1e-2+deb7u14 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
The BN_sqr implementation in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k does not properly calculate the square of a BIGNUM value, which might make it easier for remote attackers to defeat cryptographic protection mechanisms via unspecified vectors, related to crypto/bn/asm/mips.pl, crypto/bn/asm/x86_64-gcc.c, and crypto/bn/bn_asm.c.
- Published
- Jan 8, 2015
- Updated
- Jun 16, 2026
- EPSS
- 21.8% · 97th percentile
- CWE
- CWE-310
Report tools
Action score
27
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 7 / 30 · 21.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- 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 |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
Check your server's TLS configuration
The OpenSSL 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.
- openssl opensslup to 0.9.8zc inclusive
- openssl openssl1.0.0a
- openssl openssl1.0.0b
- openssl openssl1.0.0c
- openssl openssl1.0.0d
- openssl openssl1.0.0e
- openssl openssl1.0.0f
- openssl openssl1.0.0g
+12 more rows
- openssl openssl1.0.0h
- openssl openssl1.0.0i
- openssl openssl1.0.0j
- openssl openssl1.0.0k
- openssl openssl1.0.0l
- openssl openssl1.0.0m
- openssl openssl1.0.0n
- openssl openssl1.0.0o
- openssl openssl1.0.1a
- openssl openssl1.0.1b
- openssl openssl1.0.1c
- openssl openssl1.0.1d
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | openssl | before 1.0.1k-1 | 1.0.1k-1 |
| Debian:6.0 | openssl | before 0.9.8o-4squeeze19 | 0.9.8o-4squeeze19 |
| Debian:7 | openssl | before 1.0.1e-2+deb7u14 | 1.0.1e-2+deb7u14 |
| openSUSE:Tumbleweed | libressl | before 2.5.0-1.1 | 2.5.0-1.1 |
| Red Hat:enterprise_linux:6::client | openssl | before 0:1.0.1e-30.el6_6.5 | 0:1.0.1e-30.el6_6.5 |
| Red Hat:enterprise_linux:6::client | openssl-debuginfo | before 0:1.0.1e-30.el6_6.5 | 0:1.0.1e-30.el6_6.5 |
| Red Hat:enterprise_linux:6::client | openssl-devel | before 0:1.0.1e-30.el6_6.5 | 0:1.0.1e-30.el6_6.5 |
| Red Hat:enterprise_linux:6::client | openssl-perl | before 0:1.0.1e-30.el6_6.5 | 0:1.0.1e-30.el6_6.5 |
| Red Hat:enterprise_linux:6::client | openssl-static | before 0:1.0.1e-30.el6_6.5 | 0:1.0.1e-30.el6_6.5 |
| Red Hat:enterprise_linux:7::client | openssl | before 1:1.0.1e-34.el7_0.7 | 1:1.0.1e-34.el7_0.7 |
| Red Hat:enterprise_linux:7::client | openssl-debuginfo | before 1:1.0.1e-34.el7_0.7 | 1:1.0.1e-34.el7_0.7 |
| Red Hat:enterprise_linux:7::client | openssl-devel | before 1:1.0.1e-34.el7_0.7 | 1:1.0.1e-34.el7_0.7 |
| Red Hat:enterprise_linux:7::client | openssl-libs | before 1:1.0.1e-34.el7_0.7 | 1:1.0.1e-34.el7_0.7 |
| Red Hat:enterprise_linux:7::client | openssl-perl | before 1:1.0.1e-34.el7_0.7 | 1:1.0.1e-34.el7_0.7 |
| Red Hat:enterprise_linux:7::client | openssl-static | before 1:1.0.1e-34.el7_0.7 | 1:1.0.1e-34.el7_0.7 |
| SUSE:Linux Enterprise Desktop 12 | compat-openssl098 | before 0.9.8j-70.2 | 0.9.8j-70.2 |
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows…KEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code…65This week
Published before and after this one in the same product
- ← EarlierCVE-2014-3568Oct 18, 2014 · OpenSSL before 0.9.8zc, 1.0.0 before 1.0.0o, and 1.0.1 before 1.0.1j does not properly enforce the no-ssl3 build option, which allows…21Monitor
- ← EarlierCVE-2014-3569Dec 24, 2014 · The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 0.9.8zc, 1.0.0o, and 1.0.1j does not properly handle attempts to use…26Monitor
- Later →CVE-2014-3571Jan 8, 2015 · OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k allows remote attackers to cause a denial of service (NULL pointer…27Monitor
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:openssl | 1.0.1k-1 · Debian:12 | Package registry (OSV) |
| opensuse:libressl | 2.5.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:openssl | 0:1.0.1e-30.el6_6.5 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:openssl-debuginfo | 0:1.0.1e-30.el6_6.5 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:openssl-devel | 0:1.0.1e-30.el6_6.5 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:openssl-libs | 1:1.0.1e-34.el7_0.7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:openssl-perl | 0:1.0.1e-30.el6_6.5 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:openssl-static | 0:1.0.1e-30.el6_6.5 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| suse:compat-openssl098 | 0.9.8j-70.2 · SUSE:Linux Enterprise Desktop 12 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×4
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 4 repositories | 2023-11-07 |
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.
- Published
- First PoC+3224 d
- TodayNov 16, 2026+4329 d
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
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- none
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-310 · Cryptographic IssuesCVSS vector
AV:N/AC:L/Au:N/C:P/I:N/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 (19 more)Show less
- lists.apple.com/archives/security-announce/2015/Apr/msg00001.html
- lists.fedoraproject.org/pipermail/package-announce/2015-January/147938.html
- lists.fedoraproject.org/pipermail/package-announce/2015-January/148363.html
- lists.opensuse.org/opensuse-security-announce/2015-01/msg00021.html
- lists.opensuse.org/opensuse-security-announce/2015-03/msg00027.html
- lists.opensuse.org/opensuse-security-announce/2015-05/msg00026.html
- lists.opensuse.org/opensuse-security-announce/2015-07/msg00037.html
- lists.opensuse.org/opensuse-security-announce/2016-03/msg00011.html
- marc.info/?l=bugtraq&m=142496179803395&w=2
- marc.info/?l=bugtraq&m=142496289803847&w=2
- marc.info/?l=bugtraq&m=142720981827617&w=2
- marc.info/?l=bugtraq&m=142721102728110&w=2
- marc.info/?l=bugtraq&m=142895206924048&w=2
- marc.info/?l=bugtraq&m=143748090628601&w=2
- marc.info/?l=bugtraq&m=144050155601375&w=2
- marc.info/?l=bugtraq&m=144050205101530&w=2
- marc.info/?l=bugtraq&m=144050254401665&w=2
- marc.info/?l=bugtraq&m=144050297101809&w=2
- rhn.redhat.com/errata/RHSA-2015-0066.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.