Show filters
16 Total Results
Displaying 11-16 of 16
Sort by:
Attacker Value
Unknown
CVE-2020-28500
Disclosure Date: February 15, 2021 (last updated November 28, 2024)
Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.
0
Attacker Value
Unknown
CVE-2020-8203
Disclosure Date: July 15, 2020 (last updated January 21, 2024)
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
0
Attacker Value
Unknown
CVE-2019-10219
Disclosure Date: November 08, 2019 (last updated November 08, 2023)
A vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in HTML comments and instructions. This vulnerability can result in an XSS attack.
0
Attacker Value
Unknown
CVE-2019-5482
Disclosure Date: September 16, 2019 (last updated November 08, 2023)
Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
0
Attacker Value
Unknown
CVE-2019-5481
Disclosure Date: September 16, 2019 (last updated November 08, 2023)
Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.
0
Attacker Value
Unknown
CVE-2019-1559
Disclosure Date: February 26, 2019 (last updated November 08, 2023)
If an application encounters a fatal protocol error and then calls SSL_shutdown() twice (once to send a close_notify, and once to receive one) then OpenSSL can respond differently to the calling application if a 0 byte record is received with invalid padding compared to if a 0 byte record is received with an invalid MAC. If the application then behaves differently based on that in a way that is detectable to the remote peer, then this amounts to a padding oracle that could be used to decrypt data. In order for this to be exploitable "non-stitched" ciphersuites must be in use. Stitched ciphersuites are optimised implementations of certain commonly used ciphersuites. Also the application must call SSL_shutdown() twice even if a protocol error has occurred (applications should not do this but some do anyway). Fixed in OpenSSL 1.0.2r (Affected 1.0.2-1.0.2q).
0