Vulnerabilidades exploráveis hoje
415,241na 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,781
Novos KEV · 24H0
Exploit Today ≥ 701,709
Distribuição · última janela
- Crítica5,111
- Alta20,050
- Média19,099
- Baixa2,034
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2016-0079—92.4%
——28——CVE-2020-9423—92.4%
——28——CVE-2017-17969—92.4%
——28——CVE-2008-1672—92.4%
——28——CVE-2017-3069—92.4%
——28——CVE-2012-1622—92.4%
——28——CVE-2024-29275—92.4%
——28——CVE-1999-0331—92.4%
——28——CVE-2026-107967.5 ALT92.4%
——28nvm (Node Version Manager) through 0.40.4 executes arbitrary commands from version strings supplied by the configured Node.js/io.js mirror. Commands such as `nvm install` read the available versions from the mirror's index.tab and use the selected version, without sanitization, to build download URLs and shell/awk commands. Two sinks are affected by the same untrusted input: nvm_download() built a curl/wget command string and ran it with `eval`, so a version field containing command substitution (for example $(id)) was executed by the local shell; and nvm_get_checksum() interpolated the version-derived download slug into an awk program, so a crafted version could execute arbitrary commands via awk's system(). An attacker who controls the configured mirror, supplies mirror content to a user or CI on a non-default mirror, or machine-in-the-middles a non-TLS mirror can ∴ run arbitrary commands with the privileges of the user running nvm. The default mirror (https://nodejs.org over TLS) is not affected. Fixed on master (pending the next tagged release) by passing every argument as a literal argv element instead of using eval, by passing the value to awk as data via -v instead of interpolating it into the program, and by rejecting any version outside the Node.js/io.js version grammar before it is used.117dCVE-2019-19487—92.4%
——28——CVE-2020-13449—92.4%
——28——CVE-2009-3421—92.4%
——28——CVE-2017-8545—92.4%
——28——CVE-2010-1842—92.3%
——28——CVE-2019-0718—92.4%
——28——CVE-2010-2531—92.4%
——28——CVE-2021-24970—92.4%
——28——CVE-2006-1366—92.4%
——28——CVE-2000-0523—92.4%
——28——CVE-2018-8481—92.4%
——28——CVE-2018-10996—92.4%
——28——CVE-2004-1719—92.4%
——28——CVE-2006-0275—92.4%
——28——CVE-2018-12829—92.4%
——28——CVE-2018-8482—92.4%
——28——CVE-2011-0555—92.4%
——28——CVE-2014-9706—92.4%
——28——CVE-2018-15751—92.4%
——28——CVE-2020-7350—92.4%
——28——CVE-2008-2042—92.4%
——28——CVE-2024-5678—92.4%
——28——CVE-2012-3809—92.4%
——28——CVE-2012-3808—92.4%
——28——CVE-2006-0276—92.4%
——28——CVE-2017-3074—92.4%
——28——CVE-2010-2500—92.4%
——28——CVE-2020-9587—92.4%
——28——CVE-2003-1136—92.4%
——28——CVE-2024-34832—92.4%
——28——CVE-2005-1873—92.4%
——28——