Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2014-0076: The Montgomery ladder implementation in OpenSSL through 1.0.0l does not ensure that certain swap operations have a constant-time behavior…

LowCVSS 1.9 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 7/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: 0.84% (FIRST EPSS); higher than 58.5% of all records.
  • Fixed version: openssl (Debian:12) 1.0.1g-1; openssl (Debian:6.0) 0.9.8o-4squeeze15; openssl (Debian:7) 1.0.1e-2+deb7u7.

Low priority for now. Upgrade to openssl (Debian:12) 1.0.1g-1; openssl (Debian:6.0) 0.9.8o-4squeeze15; openssl (Debian:7) 1.0.1e-2+deb7u7 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 Montgomery ladder implementation in OpenSSL through 1.0.0l does not ensure that certain swap operations have a constant-time behavior, which makes it easier for local users to obtain ECDSA nonces via a FLUSH+RELOAD cache side-channel attack.

Published
Mar 25, 2014
Updated
Jun 16, 2026
EPSS
0.8% · 58th percentile

Report tools

JSON

Action score

7

Monitor

Low priority for now.

CVSS
7 / 40 · 1.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.8%

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.

Follow CVE-2014-0076

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Check your server's TLS configurationRun the SSL check

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for openssl records

Check your server's TLS configurationRun the SSL check

Is your version affected? Check it

Noroxi 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 help

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

VendorProduct
opensslopenssl

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 check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • openssl opensslup to 1.0.0l inclusive
  • openssl openssl0.9.1c
  • openssl openssl0.9.2b
  • openssl openssl0.9.3
  • openssl openssl0.9.3a
  • openssl openssl0.9.4
  • openssl openssl0.9.5
  • openssl openssl0.9.5a
+12 more rows
  • openssl openssl0.9.6
  • openssl openssl0.9.6a
  • openssl openssl0.9.6b
  • openssl openssl0.9.6c
  • openssl openssl0.9.6d
  • openssl openssl0.9.6e
  • openssl openssl0.9.6f
  • openssl openssl0.9.6g
  • openssl openssl0.9.6h
  • openssl openssl0.9.6i
  • openssl openssl0.9.6j
  • openssl openssl0.9.6k

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12opensslbefore 1.0.1g-11.0.1g-1
Debian:6.0opensslbefore 0.9.8o-4squeeze150.9.8o-4squeeze15
Debian:7opensslbefore 1.0.1e-2+deb7u71.0.1e-2+deb7u7

Same product

openssl: all records

Other 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…KEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This 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-2013-6450Jan 1, 2014 · The DTLS retransmission implementation in OpenSSL 1.0.0 before 1.0.0l and 1.0.1 before 1.0.1f does not properly maintain data structures…
    28Monitor
  • ← EarlierCVE-2013-4353Jan 8, 2014 · The ssl3_take_mac function in ssl/s3_both.c in OpenSSL 1.0.1 before 1.0.1f allows remote TLS servers to cause a denial of service (NULL…
    21Monitor
  • Later →CVE-2010-5298Apr 14, 2014 · Race condition in the ssl3_read_bytes function in s3_pkt.c in OpenSSL through 1.0.1g, when SSL_MODE_RELEASE_BUFFERS is enabled, allows…
    26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:openssl1.0.1g-1 · Debian:12Package 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

    If successful

    Confidentiality
    P · data can be read
    Integrity
    none
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    P
    Integrity impact
    None
    Availability impact
    None

    Weakness class (CWE)

    CWE-310 · Cryptographic Issues

    CVSS vector

    AV:L/AC:M/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.

    References

    Show all references (19 more)

    Vendor advisories and official records. Exploit/PoC links are deliberately left out.

    All records