CVE-2016-2107
50Vexday Risk Score
Sem sinal de exploração. Ela tem prova de conceito pública.
ssvc Attendepss 89%
da publicação à arma0 dias
Publicada no NVD5 de mai.
1ª PoC3 de mai.
probabilidade de exploração
89%top 1% das CVEs
exploração observada
nãonenhuma fonte reporta
5 exploit(s) público(s)
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a certain padding check, which allows remote attackers to obtain sensitive cleartext information via a padding-oracle attack against an AES CBC session. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-0169.
Produtos afetados
n/a · n/aPoCs públicas encontradas — 5✓ VexDay Proof
exploitdb✓ VexDay Proofwww.exploit-db.com/exploits/39768githubgithub.com/FiloSottile/CVE-2016-2107★ 193githubgithub.com/tmiklas/docker-cve-2016-2107★ 2cve_referencepacketstormsecurity.com/files/136912/Slackware-Security-Advisory-openssl-Updates.htmlnão verificadocve_referencewww.exploit-db.com/exploits/39768/não verificado⚠ Recursos públicos, para você avaliar a exposição de sistemas que controla ou está autorizado a testar. Teste apenas com autorização.
Referências
http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10759http://lists.apple.com/archives/security-announce/2016/Jul/msg00000.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2016-May/183457.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2016-May/183607.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2016-May/184605.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00001.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00008.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00011.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00013.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00014.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00016.htmlhttp://lists.opensuse.org/opensuse-security-announce/2016-05/msg00019.html