Vulnerabilidades explotables hoy
413,805en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,779
Nuevos KEV · 24H0
Exploit Today ≥ 701,707
Distribución · última ventana
- Crítico5,596
- Alto22,468
- Medio20,787
- Bajo2,126
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2008-5176—93.1%
——28——CVE-2013-2429—93.1%
——28——CVE-2008-3637—93.1%
——28——CVE-2007-6468—93.1%
——28——CVE-2016-1931—93.1%
——28——CVE-2014-0296—93.1%
——28——CVE-2013-1676—93.1%
——28——CVE-2018-19715—93.1%
——28——CVE-2010-2920—93.1%
——28——CVE-2013-1084—93.1%
——28——CVE-2011-4052—93.1%
——28——CVE-2013-6230—93.1%
——28——CVE-2009-2935—93.1%
——28——CVE-2014-0871—93.1%
——28——CVE-2018-8865—93.1%
——28——CVE-2014-0993—93.1%
——28——CVE-1999-0680—93.1%
——28——CVE-2009-0894—93.1%
——28——CVE-2019-11062—93.1%
——28——CVE-2010-2950—93.1%
——28——CVE-2021-301209.9 CRÍ93.1%
——28Kaseya VSA before 9.5.7 allows attackers to bypass the 2FA requirement. The need to use 2FA for authentication in enforce client-side instead of server-side and can be bypassed using a local proxy. Thus rendering 2FA useless. Detailed description --- During the login process, after the user authenticates with username and password, the server sends a response to the client with the booleans MFARequired and MFAEnroled. If the attacker has obtained a password of a user and used an intercepting proxy (e.g. Burp Suite) to change the value of MFARequered from True to False, there is no prompt for the second factor, but the user is still logged in.91dCVE-2019-15437.4 ALT93.1%
——28ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).10dCVE-2019-14751—93.1%
——28——CVE-2010-4647—93.1%
——28——CVE-2022-24266—93.1%
——28——CVE-2006-0663—93.1%
——28——CVE-2010-4378—93.1%
——28——CVE-2008-1195—93.1%
——28——CVE-2025-46704—93.1%
——28——CVE-2017-8857—93.1%
——28——CVE-2001-0491—93.1%
——28——CVE-2018-6211—93.1%
——28——CVE-2005-3489—93.1%
——28——CVE-2008-3971—93.1%
——28——CVE-2010-4713—93.1%
——28——CVE-2007-4473—93.1%
——28——CVE-2021-40146—93.1%
——28——CVE-2022-23267—93.1%
——28——CVE-2006-5045—93.1%
——28——CVE-2007-6060—93.1%
——28——