How severe is CVE-2014-0195?

No CVSS score has been assigned to CVE-2014-0195 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-0195?

Affected package information for CVE-2014-0195 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2014-0195?

No fixed release is recorded for CVE-2014-0195 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2014-0195 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2014-0195 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2014-0195 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2014-0195, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-0195?

CVE-2014-0195 has an EPSS (Exploit Prediction Scoring System) score of 100.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2014-0195?

CVE-2014-0195 is classified as CWE-120 (CWE-120). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-0195 published, and has it been updated?

CVE-2014-0195 was published on June 5, 2014 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2014-0195 — OpenSSL

CVE-2014-0195 is a CWE-120 vulnerability. 3 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Published

Jun 5, 2014

Updated

Apr 16, 2026

Affected

5 products

Patched

See advisory

Exploits

3 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

100.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly validate fragment lengths in DTLS ClientHello messages, which allows remote attackers to execute arbitrary code or cause a denial of service (buffer overflow and application crash) via a long non-initial fragment.

Affected Products

5 products · 8 configurations

fedorafedoraproject

2 versions

1920

Application

mariadbmariadb

≥ 10.0.0 && < 10.0.13

range

Application

opensslopenssl

≥ 1.0.1 && < 1.0.1h

range

leapopensuse

1 version

42.1

opensuseopensuse

1 version

13.2

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.…

github.comMetasploitOct 2020

The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.…

github.comGithubJun 2014

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2014-0195 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This issue does not affect the version of openssl as shipped with Red Hat Enterprise Linux 5. This issue does not affect the version of openssl098e as shipped with Red Hat Enterprise Linux 6.

Product	Fixed in	Advisory
Red Hat Enterprise Linux 6	`openssl-0:1.0.1e-16.el6_5.14`	RHSA-2014:0625
Red Hat Enterprise Linux 7	`openssl-1:1.0.1e-34.el7_0.3`	RHSA-2014:0679
Red Hat Storage 2.1	`openssl-0:1.0.1e-16.el6_5.14`	RHSA-2014:0628

Ubuntu

USN-2232-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0195 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works