Vulnerabilidades exploráveis hoje
417,457na 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,723
- Alta18,202
- Média17,900
- Baixa1,956
Filtros
Janela
Severidade
Filtros
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2012-3373—88.7%
——27——CVE-2026-826929.9 CRÍ88.7%
——27A vulnerability was found in D-Link DNS-340L and DNS-345 up to 20260717. This affects an unknown part of the file /cgi-bin/iscsi_mgr.cgi. Performing a manipulation of the argument alias/username/password/volume_location results in os command injection. It is possible to initiate the attack remotely. The exploit has been made public and could be used.80dCVE-2016-4356—88.7%
——27——CVE-2026-921828.8 ALT88.7%
——27Netgate pfSense CE XMLRPC Incorrect Authorization Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Netgate pfSense. Authentication is required to exploit this vulnerability.
The specific flaw exists within the XMLRPC endpoint. The issue results from incorrect authorization prior to allowing access to functionality. An attacker can leverage this vulnerability to execute code within the context of the root. Was ZDI-CAN-32353.22hCVE-2024-47419.8 CRÍ88.7%
——27Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause
memory to be accessed that was previously freed in some situations
Impact summary: A use after free can have a range of potential consequences such
as the corruption of valid data, crashes or execution of arbitrary code.
However, only applications that directly call the SSL_free_buffers function are
affected by this issue. Applications that do not call this function are not
vulnerable. Our investigations indicate that this function is rarely used by
applications.
The SSL_free_buffers function is used to free the internal OpenSSL buffer used
when processing an incoming record from the network. The call is only expected
to succeed if the buffer is not currently in use. However, two scenarios have
been identified where the buffer is freed even when still in use.
The first scenario occurs where a record header has been received from the
network and processed by OpenSSL, but the full record body has not yet arrived.
In this case calling SSL_free_buffers will succeed even though a record has only
been partially processed and the buffer is still in use.
The second scenario occurs where a full record containing application data has
been received and processed by OpenSSL but the application has only read part of
this data. Again a call to SSL_free_buffers will succeed even though the buffer
is still in use.
While these scenarios could occur accidentally during normal operation a
malicious attacker could attempt to engineer a stituation where this occurs.
We are not aware of this issue being actively exploited.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.10dCVE-2017-11102—88.7%
——27——CVE-2010-3711—88.7%
——27——CVE-2007-2326—88.7%
——27——CVE-2005-1813—88.7%
——27——CVE-2019-8242—88.7%
——27——CVE-2019-3994—88.7%
——27——CVE-2016-5449—88.7%
——27——CVE-2017-2826—88.7%
——27——CVE-2022-26831—88.7%
——27——CVE-2018-8374—88.7%
——27——CVE-2007-2441—88.6%
——27——CVE-2013-4933—88.7%
——27——CVE-2003-0565—88.7%
——27——CVE-2021-20610—88.7%
——27——CVE-2007-2060—88.7%
——27——CVE-2019-2988—88.6%
——27——CVE-2019-8244—88.7%
——27——CVE-2013-5038—88.7%
——27——CVE-2013-4932—88.7%
——27——CVE-2019-10958—88.7%
——27——CVE-2004-2520—88.7%
——27——CVE-2024-56512—88.6%
——27——CVE-2015-6171—88.6%
——27——CVE-2024-38147—88.6%
——27——CVE-2011-5053—88.6%
——27——CVE-2004-0961—88.6%
——27——CVE-2011-1208—88.6%
——27——CVE-2020-13929—88.6%
——27——CVE-2023-35638—88.6%
——27——CVE-2007-0109—88.6%
——27——CVE-2017-18734—88.6%
——27——CVE-2012-1199—88.6%
——27——CVE-2001-1380—88.6%
——27——CVE-2006-0857—88.6%
——27——CVE-2001-0285—88.6%
——27——