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 version has been published for CVE-2014-0195 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

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 92.8%, 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.

CVE-2014-0195

Published

Jun 5, 2014

Updated

Apr 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

92.8%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0195 in your stack?

O3 detects CVE-2014-0195 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works