How severe is CVE-2014-3566?

CVE-2014-3566 has a CVSS score of 3.4/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2014-3566?

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

How do I fix CVE-2014-3566?

No fixed version has been published for CVE-2014-3566 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-3566 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2014-3566, including 4 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-3566?

CVE-2014-3566 has an EPSS (Exploit Prediction Scoring System) score of 93.5%, 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.

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

CVE-2014-3566 was published on October 15, 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-3566

LOW

Published

Oct 15, 2014

Updated

Apr 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

5 known

EPSS Exploitation Probability

via FIRST.org ↗

93.5%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 SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, aka the "POODLE" issue.

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 SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other produc…

github.comMetasploitJan 2021

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other produc…

github.comGithubFeb 2015

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other produc…

github.comGithubOct 2014

The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other produc…

github.comMetasploitNov 2022

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3566 in your stack?

O3 detects CVE-2014-3566 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