Vulnerabilidades exploráveis hoje
419,076na 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ítica4,738
- Alta18,304
- Média18,049
- Baixa1,972
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2004-0034—86.3%
——26——CVE-2024-42845—86.3%
——26——CVE-2015-3270—86.3%
——26——CVE-2007-1299—86.3%
——26——CVE-2017-6349—86.3%
——26——CVE-2012-1110—86.3%
——26——CVE-2014-6386—86.3%
——26——CVE-2014-9635—86.3%
——26——CVE-2022-22019—86.3%
——26——CVE-2014-9634—86.3%
——26——CVE-2022-21957—86.3%
——26——CVE-2022-352606.5 MÉD86.3%
——26curl can be told to parse a `.netrc` file for credentials. If that file endsin a line with 4095 consecutive non-white space letters and no newline, curlwould first read past the end of the stack-based buffer, and if the readworks, write a zero byte beyond its boundary.This will in most cases cause a segfault or similar, but circumstances might also cause different outcomes.If a malicious user can provide a custom netrc file to an application or otherwise affect its contents, this flaw could be used as denial-of-service.38dCVE-2014-5342—86.3%
——26——CVE-2012-3443—86.3%
——26——CVE-2022-435525.9 MÉD86.3%
——26A use after free vulnerability exists in curl <7.87.0. Curl can be asked to *tunnel* virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path.29dCVE-2012-0864—86.3%
——26——CVE-2020-9730—86.3%
——26——CVE-2007-5488—86.3%
——26——CVE-2017-12754—86.3%
——26——CVE-2020-9729—86.3%
——26——CVE-2019-9584—86.3%
——26——CVE-2017-14726—86.3%
——26——CVE-2003-0064—86.3%
——26——CVE-2002-2366—86.3%
——26——CVE-2015-5813—86.3%
——26——CVE-2015-5810—86.3%
——26——CVE-2021-327517.5 ALT86.3%
——26Gradle is a build tool with a focus on build automation. In versions prior to 7.2, start scripts generated by the `application` plugin and the `gradlew` script are both vulnerable to arbitrary code execution when an attacker is able to change environment variables for the user running the script. This may impact those who use `gradlew` on Unix-like systems or use the scripts generated by Gradle in thieir application on Unix-like systems. For this vulnerability to be exploitable, an attacker needs to be able to set the value of particular environment variables and have those environment variables be seen by the vulnerable scripts. This issue has been patched in Gradle 7.2 by removing the use of `eval` and requiring the use of the `bash` shell. There are a few workarounds available. For CI/CD systems using the Gradle build tool, one may ensure that untrusted users are unable to change environment variables for the user that executes `gradlew`. If one is unable to upgrade to Gradle 7.2, one may generate a new `gradlew` script with Gradle 7.2 and use it for older versions of Gradle. Fpplications using start scripts generated by Gradle, one may ensure that untrusted users are unable to change environment variables for the user that executes the start script. A vulnerable start script could be manually patched to remove the use of `eval` or the use of environment variables that affect the application's command-line. If the application is simple enough, one may be able to avoid the use of the start scripts by running the application directly with Java command.44dCVE-2023-26418—86.3%
——26——CVE-2017-14767—86.3%
——26——CVE-2019-9585—86.3%
——26——CVE-2005-0127—86.3%
——26——CVE-2020-25287—86.3%
——26——CVE-2017-7701—86.3%
——26——CVE-2017-12159—86.3%
——26——CVE-2019-7038—86.3%
——26——CVE-2022-27346—86.3%
——26——CVE-2000-0167—86.3%
——26——CVE-2020-9728—86.3%
——26——CVE-2010-3304—86.3%
——26——CVE-2022-27352—86.3%
——26——