PULSE
FEED
ransomaurora reclama a William Cook Holdings Limited · GB · Manufacturingransomakira reclama a Pecora · IT · Otherransombarracuda reclama a Dallas Theological Seminary · US · Educationransomblackout reclama a wakao.co.jp · JP · Otherransomincransom reclama a eni.it · IT · Energy & Utilitiesransomspacebears reclama a Inlandboatmen’s Union of the Pacific — Marine Division of the ILWU · US · Transportationransomspacebears reclama a SDJ Design Engineering Limited · GB · Manufacturingransomspacebears reclama a Rise | A Community Service Partnership (also known as NJ Rise) · US · Otherransomspacebears reclama a Epoch Residential · US · Hospitalityransomincransom reclama a Boeing · US · Government & Defenseransomhandsome boy hacking club reclama a FIFA (Fédération Internationale de Football Association) · CH · Otherransomrhysida reclama a Rudolph F. Jass, Jr., PLLC · US · Professional Servicesransomsilentransomgroup reclama a J... W...ransominception reclama a AutoZone, Inc. · US · Retail & E-Commerceransomaurora reclama a William Cook Holdings Limited · GB · Manufacturingransomakira reclama a Pecora · IT · Otherransombarracuda reclama a Dallas Theological Seminary · US · Educationransomblackout reclama a wakao.co.jp · JP · Otherransomincransom reclama a eni.it · IT · Energy & Utilitiesransomspacebears reclama a Inlandboatmen’s Union of the Pacific — Marine Division of the ILWU · US · Transportationransomspacebears reclama a SDJ Design Engineering Limited · GB · Manufacturingransomspacebears reclama a Rise | A Community Service Partnership (also known as NJ Rise) · US · Otherransomspacebears reclama a Epoch Residential · US · Hospitalityransomincransom reclama a Boeing · US · Government & Defenseransomhandsome boy hacking club reclama a FIFA (Fédération Internationale de Football Association) · CH · Otherransomrhysida reclama a Rudolph F. Jass, Jr., PLLC · US · Professional Servicesransomsilentransomgroup reclama a J... W...ransominception reclama a AutoZone, Inc. · US · Retail & E-Commerce
CVE Watch418.896 no arquivo completo

Vulnerabilidades exploráveis hoje

418,896na visualização atual

Score único que combina CVSS, presença no KEV e EPSS. Cada CVE com sua própria ficha — timeline da publicação até a exploração ativa.

No catálogo KEV1,786
Novos KEV · 24H0
Exploit Today ≥ 701,715

Distribuição · última janela

  • Crítica
    4,731
  • Alta
    18,267
  • Média
    18,078
  • Baixa
    1,977
Filtros
Filtros

Janela

Severidade

Filtros

Vulnerabilidades47,841–47,880 · 418,896
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2018-19705—
88.4%
——27——
CVE-2018-5154—
88.4%
——27——
CVE-2020-25270—
88.4%
——27——
CVE-1999-0775—
88.4%
——27——
CVE-2025-24076—
88.4%
——27——
CVE-2009-0398—
88.4%
——27——
CVE-2009-1912—
88.4%
——27——
CVE-2019-18666—
88.4%
——27——
CVE-2017-9111—
88.4%
——27——
CVE-2017-90477.5 ALT
88.4%
——27A buffer overflow was discovered in libxml2 20904-GITv2.9.4-16-g0741801. The function xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a char buffer 'buf' of size 'size'. The variable len is assigned strlen(buf). If the content->type is XML_ELEMENT_CONTENT_ELEMENT, then (i) the content->prefix is appended to buf (if it actually fits) whereupon (ii) content->name is written to the buffer. However, the check for whether the content->name actually fits also uses 'len' rather than the updated buffer length strlen(buf). This allows us to write about "size" many bytes beyond the allocated memory. This vulnerability causes programs that use libxml2, such as PHP, to crash.37d
CVE-2015-2789—
88.4%
——27——
CVE-2008-1245—
88.4%
——27——
CVE-2010-2443—
88.4%
——27——
CVE-2021-21041—
88.4%
——27——
CVE-2021-21702—
88.4%
——27——
CVE-2021-34552—
88.4%
——27——
CVE-2020-2760—
88.4%
——27——
CVE-2016-5264—
88.4%
——27——
CVE-2020-3292—
88.4%
——27——
CVE-2017-11468—
88.4%
——27——
CVE-2020-3286—
88.4%
——27——
CVE-2016-1000343—
88.4%
——27——
CVE-2018-16033—
88.4%
——27——
CVE-2018-16032—
88.4%
——27——
CVE-2014-9375—
88.4%
——27——
CVE-2020-3294—
88.4%
——27——
CVE-2017-14125—
88.4%
——27——
CVE-2021-21040—
88.4%
——27——
CVE-2021-27692—
88.4%
——27——
CVE-2018-15984—
88.4%
——27——
CVE-2006-5555—
88.4%
——27——
CVE-2004-0468—
88.4%
——27——
CVE-1999-0495—
88.4%
——27——
CVE-2007-0279—
88.4%
——27——
CVE-2015-2170—
88.4%
——27——
CVE-2015-2194—
88.4%
——27——
CVE-2018-10392—
88.4%
——27——
CVE-2019-7108—
88.4%
——27——
CVE-2025-24132—
88.4%
——27——
CVE-2024-07275.5 MÉD
88.4%
——27Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly. A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue. OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass(). We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant. The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.37d