Vulnerabilidades do Netapp Ontap 9
🔔 Criar alerta RSS Verificador de versão
CVEs publicadas que afetam Netapp Ontap 9: 5 registro(s), com versões afetadas e correções.cpe:2.3:a:netapp:ontap_9
CVE-2026-22052
Média · 4.3
CWE-209 04/03/2026
Information Exposure Through an Error Message em Netapp Ontap
ONTAP versions 9.12.1 and higher with S3 NAS buckets are susceptible to an information disclosure vulnerability. Successful exploit could allow an authenticated attacker to view a listing of the contents in a directory for which they lack permission.
CVE-2026-22050
Média · 4.3
CWE-639 12/01/2026
Authorization Bypass Through User-Controlled Key (IDOR) em Netapp Ontap
ONTAP versions 9.16.1 prior to 9.16.1P9 and 9.17.1 prior to 9.17.1P2 with snapshot locking enabled are susceptible to a vulnerability which could allow a privileged remote attacker to set the snapshot expiry time to none.
CVE-2024-38475
Crítica · 9.1
KEV Urgente · 73 Exploit público CWE-116 01/07/2024
Apache HTTP Server Improper Escaping of Output Vulnerability
Improper escaping of output in mod_rewrite in Apache HTTP Server 2.4.59 and earlier allows an attacker to map URLs to filesystem locations that are permitted to be served by the server but are not intentionally/directly reachable by any URL, resulting in code execution or source code disclosure.
Substitutions in server context that use a backreferences or variables as the first segment of the substitution are affected. Some unsafe RewiteRules will be broken by this change and the rewrite flag "UnsafePrefixStat" can be used to opt back in once ensuring the substitution is appropriately constrained.
CVE-2023-27535
Média · 5.9
CWE-287 30/03/2023
An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse...
An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information.
CVE-2022-42915
Alta · 8.1
CWE-415 29/10/2022
curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a...
curl before 7.86.0 has a double free. If curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL, it sets up the connection to the remote server by issuing a CONNECT request to the proxy, and then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200 status code to the client. Due to flaws in the error/cleanup handling, this could trigger a double free in curl if one of the following schemes were used in the URL for the transfer: dict, gopher, gophers, ldap, ldaps, rtmp, rtmps, or telnet. The earliest affected version is 7.77.0.