Show filters
55 Total Results
Displaying 51-55 of 55
Sort by:
Attacker Value
Unknown
CVE-2015-2774
Disclosure Date: April 07, 2016 (last updated November 25, 2024)
Erlang/OTP before 18.0-rc1 does not properly check CBC padding bytes when terminating connections, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, a variant of CVE-2014-3566 (aka POODLE).
0
Attacker Value
Unknown
CVE-2014-1693
Disclosure Date: December 08, 2014 (last updated October 05, 2023)
Multiple CRLF injection vulnerabilities in the FTP module in Erlang/OTP R15B03 allow context-dependent attackers to inject arbitrary FTP commands via CRLF sequences in the (1) user, (2) account, (3) cd, (4) ls, (5) nlist, (6) rename, (7) delete, (8) mkdir, (9) rmdir, (10) recv, (11) recv_bin, (12) recv_chunk_start, (13) send, (14) send_bin, (15) send_chunk_start, (16) append_chunk_start, (17) append, or (18) append_bin command.
0
Attacker Value
Unknown
CVE-2014-2829
Disclosure Date: April 11, 2014 (last updated October 05, 2023)
Erlang Solutions MongooseIM through 1.3.1 rev. 2 does not properly restrict the processing of compressed XML elements, which allows remote attackers to cause a denial of service (resource consumption) via a crafted XMPP stream, aka an "xmppbomb" attack.
0
Attacker Value
Unknown
CVE-2011-0766
Disclosure Date: May 31, 2011 (last updated October 04, 2023)
The random number generator in the Crypto application before 2.0.2.2, and SSH before 2.0.5, as used in the Erlang/OTP ssh library before R14B03, uses predictable seeds based on the current time, which makes it easier for remote attackers to guess DSA host and SSH session keys.
0
Attacker Value
Unknown
CVE-2009-0130
Disclosure Date: January 15, 2009 (last updated November 08, 2023)
lib/crypto/c_src/crypto_drv.c in erlang does not properly check the return value from the OpenSSL DSA_do_verify function, which might allow remote attackers to bypass validation of the certificate chain via a malformed SSL/TLS signature, a similar vulnerability to CVE-2008-5077. NOTE: a package maintainer disputes this issue, reporting that there is a proper check within the only code that uses the applicable part of crypto_drv.c, and thus "this report is invalid.
0