LiveActive security incident?Get immediate response
CVE Record

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...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a legacy OpenSSL cryptographic correctness flaw. Some affected versions could calculate a large-number square incorrectly, potentially weakening cryptographic protections. The source bundle does not provide a CVSS score, specific attack path, or evidence of active exploitation, so urgency depends on whether old OpenSSL builds remain in use. Exposure is most likely in legacy servers, appliances, embedded products, or applications still using affected OpenSSL versions or statically bundled OpenSSL. Vendor advisories from Cisco, HP, Apple, Oracle, openSUSE, Fedora, Red Hat, and others indicate downstream product impact existed in 2015-era software. Prioritize discovery first. This is old, but cryptographic library flaws can persist in appliances and bundled software. Escalate remediation for internet-facing, VPN, TLS, signing, or authentication systems still using affected OpenSSL versions. Mitigation focus: Upgrade OpenSSL to 0.9.8zd, 1.0.0p, 1.0.1k, or later supported releases.; Apply relevant operating system and vendor security advisories for affected products.; Identify and update applications that statically bundle vulnerable OpenSSL code..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2014-3570 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.