PULSE
FEED
ransomrhysida reclama a SteelTech Inc. · Manufacturingransomemperador reclama a Scooter Autoservice gmbh · DE · Transportationransomhyflock reclama a bestcorp · INransomhyflock reclama a ASIA FM Taiwan Inc · TW · Technologyransomthegentlemen reclama a AARP · US · Healthcareransomthegentlemen reclama a NVIDIA · US · Technologyransompixelleaks reclama a EKwiiK (EazyPay, ekwiik.com) · KE · Financial Servicesransompixelleaks reclama a Seguridad Reyna (REYA) · MX · Professional Servicesransompixelleaks reclama a FAIR Health, Inc. (fairhealth.com) · US · Healthcareransompixelleaks reclama a Wei Tai Leather Viet Nam Co., Ltd (weitai-leather.com) · VN · Manufacturingransomaoqin reclama a TopGroup · ARransomhelix reclama a Mnfhsransomqilin reclama a Meridian Capital Group · US · Financial Servicesransompixelleaks reclama a KDBS Solutions (client hosting) · Technologyransomrhysida reclama a SteelTech Inc. · Manufacturingransomemperador reclama a Scooter Autoservice gmbh · DE · Transportationransomhyflock reclama a bestcorp · INransomhyflock reclama a ASIA FM Taiwan Inc · TW · Technologyransomthegentlemen reclama a AARP · US · Healthcareransomthegentlemen reclama a NVIDIA · US · Technologyransompixelleaks reclama a EKwiiK (EazyPay, ekwiik.com) · KE · Financial Servicesransompixelleaks reclama a Seguridad Reyna (REYA) · MX · Professional Servicesransompixelleaks reclama a FAIR Health, Inc. (fairhealth.com) · US · Healthcareransompixelleaks reclama a Wei Tai Leather Viet Nam Co., Ltd (weitai-leather.com) · VN · Manufacturingransomaoqin reclama a TopGroup · ARransomhelix reclama a Mnfhsransomqilin reclama a Meridian Capital Group · US · Financial Servicesransompixelleaks reclama a KDBS Solutions (client hosting) · Technology
CVE Watch416.768 no arquivo completo

Vulnerabilidades exploráveis hoje

416,768na 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,782
Novos KEV · 24H0
Exploit Today ≥ 701,710

Distribuição · última janela

  • Crítica
    4,862
  • Alta
    19,093
  • Média
    18,288
  • Baixa
    2,015
Filtros
Filtros

Janela

Severidade

Filtros

Vulnerabilidades35,641–35,680 · 416,768
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2020-14579—
91.3%
——27——
CVE-2013-5878—
91.3%
——27——
CVE-2026-463337.1 ALT
91.3%
——27In the Linux kernel, the following vulnerability has been resolved: ptrace: slightly saner 'get_dumpable()' logic The 'dumpability' of a task is fundamentally about the memory image of the task - the concept comes from whether it can core dump or not - and makes no sense when you don't have an associated mm. And almost all users do in fact use it only for the case where the task has a mm pointer. But we have one odd special case: ptrace_may_access() uses 'dumpable' to check various other things entirely independently of the MM (typically explicitly using flags like PTRACE_MODE_READ_FSCREDS). Including for threads that no longer have a VM (and maybe never did, like most kernel threads). It's not what this flag was designed for, but it is what it is. The ptrace code does check that the uid/gid matches, so you do have to be uid-0 to see kernel thread details, but this means that the traditional "drop capabilities" model doesn't make any difference for this all. Make it all make a *bit* more sense by saying that if you don't have a MM pointer, we'll use a cached "last dumpability" flag if the thread ever had a MM (it will be zero for kernel threads since it is never set), and require a proper CAP_SYS_PTRACE capability to override.8d
CVE-2015-6486—
91.3%
——27——
CVE-2021-21033—
91.3%
——27——
CVE-2020-27153—
91.3%
——27——
CVE-2021-21035—
91.3%
——27——
CVE-2006-6976—
91.3%
——27——
CVE-2011-2871—
91.3%
——27——
CVE-2019-0836—
91.3%
——27——
CVE-2011-2833—
91.3%
——27——
CVE-2015-8917—
91.3%
——27——
CVE-2011-2869—
91.3%
——27——
CVE-2020-7064—
91.3%
——27——
CVE-2019-0962—
91.3%
——27——
CVE-2019-1010287—
91.3%
——27——
CVE-2004-0801—
91.3%
——27——
CVE-2006-0502—
91.3%
——27——
CVE-2019-20421—
91.3%
——27——
CVE-2020-28243—
91.3%
——27——
CVE-2016-8367—
91.3%
——27——
CVE-2019-14243—
91.3%
——27——
CVE-2022-4093—
91.3%
——27——
CVE-2004-2758—
91.3%
——27——
CVE-2016-4195—
91.3%
——27——
CVE-2001-0494—
91.3%
——27——
CVE-2012-0853—
91.3%
——27——
CVE-2017-8223—
91.3%
——27——
CVE-2011-2873—
91.3%
——27——
CVE-2011-2912—
91.3%
——27——
CVE-2021-44030—
91.3%
——27——
CVE-2005-2522—
91.3%
——27——
CVE-2008-3361—
91.3%
——27——
CVE-2002-0556—
91.3%
——27——
CVE-1999-0241—
91.3%
——27——
CVE-2011-2872—
91.3%
——27——
CVE-2024-29204—
91.3%
——27——
CVE-2009-1938—
91.3%
——27——
CVE-2019-6735—
91.3%
——27——
CVE-2012-4231—
91.3%
——27——