PULSE
FEED
ransombarracuda reclama a EVINOKS · TR · Technologyransomqilin reclama a Danser · US · Otherransomvexy ransomware reclama a System Soft · BG · Technologyransomvexy ransomware reclama a JHAMF Group · BDransomemperador reclama a Punta Shopping · BR · Retail & E-Commerceransomnightspire reclama a **F*A *.Aransompayload reclama a Straze Garden Center · Retail & E-Commerceransompayload reclama a Kraft Lernen · DE · Educationransompayload reclama a SALEG (Sachsen-Anhaltische Landesentwicklungsgesellschaft mbH) · DE · Government & Defenseransomrhysida reclama a Phoenix Charter Academy · US · Educationransomauditteam reclama a Pe***CT · NLransomauditteam reclama a jl***om · SGransomauditteam reclama a hn***rgransomauditteam reclama a ro***upransombarracuda reclama a EVINOKS · TR · Technologyransomqilin reclama a Danser · US · Otherransomvexy ransomware reclama a System Soft · BG · Technologyransomvexy ransomware reclama a JHAMF Group · BDransomemperador reclama a Punta Shopping · BR · Retail & E-Commerceransomnightspire reclama a **F*A *.Aransompayload reclama a Straze Garden Center · Retail & E-Commerceransompayload reclama a Kraft Lernen · DE · Educationransompayload reclama a SALEG (Sachsen-Anhaltische Landesentwicklungsgesellschaft mbH) · DE · Government & Defenseransomrhysida reclama a Phoenix Charter Academy · US · Educationransomauditteam reclama a Pe***CT · NLransomauditteam reclama a jl***om · SGransomauditteam reclama a hn***rgransomauditteam reclama a ro***up
CVE Watch406,265 en archivo total

Vulnerabilidades explotables hoy

406,265en 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,766
Nuevos KEV · 24H0
Exploit Today ≥ 701,698

Distribución · última ventana

  • Crítico
    5,569
  • Alto
    21,655
  • Medio
    20,169
  • Bajo
    2,097
Filtros
Filtros

Ventana

Severidad

Filtros

Vulnerabilidades11,721–11,760 · 406,265
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2022-30063—
97.2%
——29——
CVE-2020-27019—
97.2%
——29——
CVE-2014-8801—
97.2%
——29——
CVE-2018-4243—
97.2%
——29——
CVE-2022-208667.4 ALT
97.2%
——29A vulnerability in the handling of RSA keys on devices running Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to retrieve an RSA private key. This vulnerability is due to a logic error when the RSA key is stored in memory on a hardware platform that performs hardware-based cryptography. An attacker could exploit this vulnerability by using a Lenstra side-channel attack against the targeted device. A successful exploit could allow the attacker to retrieve the RSA private key. The following conditions may be observed on an affected device: This vulnerability will apply to approximately 5 percent of the RSA keys on a device that is running a vulnerable release of Cisco ASA Software or Cisco FTD Software; not all RSA keys are expected to be affected due to mathematical calculations applied to the RSA key. The RSA key could be valid but have specific characteristics that make it vulnerable to the potential leak of the RSA private key. If an attacker obtains the RSA private key, they could use the key to impersonate a device that is running Cisco ASA Software or Cisco FTD Software or to decrypt the device traffic. See the Indicators of Compromise section for more information on the detection of this type of RSA key. The RSA key could be malformed and invalid. A malformed RSA key is not functional, and a TLS client connection to a device that is running Cisco ASA Software or Cisco FTD Software that uses the malformed RSA key will result in a TLS signature failure, which means a vulnerable software release created an invalid RSA signature that failed verification. If an attacker obtains the RSA private key, they could use the key to impersonate a device that is running Cisco ASA Software or Cisco FTD Software or to decrypt the device traffic.82d
CVE-2009-1331—
97.2%
——29——
CVE-2024-0264—
97.2%
——29——
CVE-2023-5642—
97.2%
——29——
CVE-2015-2505—
97.2%
——29——
CVE-2022-24314—
97.2%
——29——
CVE-2016-7277—
97.2%
——29——
CVE-2025-32103—
97.2%
——29——
CVE-2017-0196—
97.2%
——29——
CVE-2014-1811—
97.2%
——29——
CVE-2019-0220—
97.2%
——29——
CVE-2019-8046—
97.2%
——29——
CVE-2017-8957—
97.2%
——29——
CVE-2015-2451—
97.2%
——29——
CVE-2023-0234—
97.2%
——29——
CVE-2001-0609—
97.2%
——29——
CVE-2021-31249—
97.2%
——29——
CVE-2007-2788—
97.2%
——29——
CVE-2001-0664—
97.2%
——29——
CVE-2024-0717—
97.2%
——29——
CVE-2001-0328—
97.2%
——29——
CVE-2015-6107—
97.2%
——29——
CVE-2024-29990—
97.2%
——29——
CVE-2006-3660—
97.2%
——29——
CVE-2017-5820—
97.2%
——29——
CVE-2017-2984—
97.2%
——29——
CVE-2012-2031—
97.2%
——29——
CVE-2022-40152—
97.2%
——29——
CVE-2008-3544—
97.2%
——29——
CVE-2002-0697—
97.2%
——29——
CVE-1999-0385—
97.2%
——29——
CVE-2019-7670—
97.2%
——29——
CVE-2017-8975—
97.2%
——29——
CVE-2022-35413—
97.2%
——29——
CVE-2025-8723—
97.2%
——29——
CVE-2020-7012—
97.2%
——29——