CVE-2024-38475 Vulnerability Analysis & Exploit Details

CVE-2024-38475
Vulnerability Scoring

9.1
/10
Critical Risk

As a catastrophic security flaw, CVE-2024-38475 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-38475 Details

Status: Analyzed

Last updated: 🕤 17 Nov 2025, 21:49 UTC
Originally published on: 🕖 01 Jul 2024, 19:15 UTC

Time between publication and last update: 504 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVE-2024-38475 Vulnerability Summary

CVE-2024-38475: 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.

Assessing the Risk of CVE-2024-38475

Access Complexity Graph

The exploitability of CVE-2024-38475 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-38475

With low attack complexity and no required privileges, CVE-2024-38475 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-38475, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-38475, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2024-38475 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2024-38475 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2024-38475 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.043% (probability of exploit)

EPSS Percentile: 12.0% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 88.0% of others.

CVE-2024-38475 References

External References

CWE Common Weakness Enumeration

CWE-116

CAPEC Common Attack Pattern Enumeration and Classification

  • Cross Zone Scripting CAPEC-104 An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security.
  • User-Controlled Filename CAPEC-73 An attack of this type involves an adversary inserting malicious characters (such as a XSS redirection) into a filename, directly or indirectly that is then used by the target software to generate HTML text or other potentially executable content. Many websites rely on user-generated content and dynamically build resources like files, filenames, and URL links directly from user supplied data. In this attack pattern, the attacker uploads code that can execute in the client browser and/or redirect the client browser to a site that the attacker owns. All XSS attack payload variants can be used to pass and exploit these vulnerabilities.
  • Web Server Logs Tampering CAPEC-81 Web Logs Tampering attacks involve an attacker injecting, deleting or otherwise tampering with the contents of web logs typically for the purposes of masking other malicious behavior. Additionally, writing malicious data to log files may target jobs, filters, reports, and other agents that process the logs in an asynchronous attack pattern. This pattern of attack is similar to "Log Injection-Tampering-Forging" except that in this case, the attack is targeting the logs of the web server and not the application.
  • AJAX Footprinting CAPEC-85 This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.

Vulnerable Configurations

  • cpe:2.3:a:apache:http_server:2.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.5:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.5:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.6:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.7:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.7:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.8:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.8:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.9:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.9:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.10:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.10:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.11:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.11:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.12:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.12:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.13:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.13:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.14:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.14:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.15:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.15:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.16:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.16:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.17:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.17:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.18:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.18:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.19:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.19:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.20:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.20:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.21:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.21:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.22:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.22:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.23:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.23:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.24:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.24:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.25:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.25:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.26:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.26:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.27:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.27:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.28:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.28:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.29:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.29:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.30:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.30:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.31:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.31:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.32:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.32:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.33:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.33:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.34:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.34:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.35:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.35:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.36:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.36:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.37:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.37:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.38:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.38:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.39:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.39:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.40:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.40:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.41:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.41:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.42:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.42:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.43:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.43:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.44:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.44:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.45:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.45:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.46:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.46:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.47:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.47:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.48:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.48:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.49:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.49:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.50:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.50:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.51:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.51:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.52:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.52:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.53:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.53:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.54:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.54:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.55:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.55:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.56:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.56:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.57:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.57:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.58:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.58:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:http_server:2.4.59:*:*:*:*:*:*:*
    cpe:2.3:a:apache:http_server:2.4.59:*:*:*:*:*:*:*
  • cpe:2.3:a:netapp:ontap_9:-:*:*:*:*:*:*:*
    cpe:2.3:a:netapp:ontap_9:-:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:9.0.0.10-28sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:9.0.0.10-28sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:9.0.0.11-31sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:9.0.0.11-31sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:10.2.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:10.2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:10.2.0.7-34sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:10.2.0.7-34sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:10.2.0.8-37sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:10.2.0.8-37sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:10.2.1.0-17sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:10.2.1.0-17sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:10.2.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:10.2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:10.2.1.1-19sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:10.2.1.1-19sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:10.2.1.10-62sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:10.2.1.10-62sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_200_firmware:10.2.1.11-65sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_200_firmware:10.2.1.11-65sv:*:*:*:*:*:*:*
  • cpe:2.3:h:sonicwall:sma_200:-:*:*:*:*:*:*:*
    cpe:2.3:h:sonicwall:sma_200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:8.0.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:8.0.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:9.0.0.10:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:9.0.0.10:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:9.0.0.10-28sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:9.0.0.10-28sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:9.0.0.11-31sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:9.0.0.11-31sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:10.2.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:10.2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:10.2.0.7-34sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:10.2.0.7-34sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:10.2.0.8-37sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:10.2.0.8-37sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:10.2.0.9-41sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:10.2.0.9-41sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:10.2.1.0-17sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:10.2.1.0-17sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:10.2.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:10.2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:10.2.1.1-19sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:10.2.1.1-19sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:10.2.1.10-62sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:10.2.1.10-62sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_210_firmware:10.2.1.11-65sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_210_firmware:10.2.1.11-65sv:*:*:*:*:*:*:*
  • cpe:2.3:h:sonicwall:sma_210:-:*:*:*:*:*:*:*
    cpe:2.3:h:sonicwall:sma_210:-:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:9.0.0.10-28sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:9.0.0.10-28sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:9.0.0.11-31sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:9.0.0.11-31sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:10.2.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:10.2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:10.2.0.7-34sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:10.2.0.7-34sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:10.2.0.8-37sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:10.2.0.8-37sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:10.2.1.0-17sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:10.2.1.0-17sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:10.2.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:10.2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:10.2.1.1-19sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:10.2.1.1-19sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:10.2.1.10-62sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:10.2.1.10-62sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_400_firmware:10.2.1.11-65sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_400_firmware:10.2.1.11-65sv:*:*:*:*:*:*:*
  • cpe:2.3:h:sonicwall:sma_400:-:*:*:*:*:*:*:*
    cpe:2.3:h:sonicwall:sma_400:-:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:8.0.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:8.0.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:9.0.0.10:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:9.0.0.10:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:9.0.0.10-28sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:9.0.0.10-28sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:9.0.0.11-31sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:9.0.0.11-31sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:10.2.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:10.2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:10.2.0.7-34sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:10.2.0.7-34sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:10.2.0.8-37sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:10.2.0.8-37sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:10.2.0.9-41sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:10.2.0.9-41sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:10.2.1.0-17sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:10.2.1.0-17sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:10.2.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:10.2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:10.2.1.1-19sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:10.2.1.1-19sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:10.2.1.10-62sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:10.2.1.10-62sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_410_firmware:10.2.1.11-65sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_410_firmware:10.2.1.11-65sv:*:*:*:*:*:*:*
  • cpe:2.3:h:sonicwall:sma_410:-:*:*:*:*:*:*:*
    cpe:2.3:h:sonicwall:sma_410:-:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:8.0.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:8.0.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:9.0.0.10:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:9.0.0.10:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:9.0.0.10-28sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:9.0.0.10-28sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:9.0.0.11-31sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:9.0.0.11-31sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:9.0.0.9-26sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:9.0.0.9-26sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:10.2.0.8-37sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:10.2.0.8-37sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:10.2.0.9-41sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:10.2.0.9-41sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:10.2.1.1-19sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:10.2.1.1-19sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:10.2.1.10-62sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:10.2.1.10-62sv:*:*:*:*:*:*:*
  • cpe:2.3:o:sonicwall:sma_500v_firmware:10.2.1.11-65sv:*:*:*:*:*:*:*
    cpe:2.3:o:sonicwall:sma_500v_firmware:10.2.1.11-65sv:*:*:*:*:*:*:*
  • cpe:2.3:h:sonicwall:sma_500v:-:*:*:*:*:*:*:*
    cpe:2.3:h:sonicwall:sma_500v:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-38475: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-66026 – REDAXO is a PHP-based CMS. Prior to version 5.20.1, a reflected Cross-Site Scripting (XSS) vulnerability exists in the Mediapool view where the req...
  • CVE-2025-66025 – Caido is a web security auditing toolkit. Prior to version 0.53.0, the Markdown renderer used in Caido’s Findings page improperly handled user-supp...
  • CVE-2025-66022 – FACTION is a PenTesting Report Generation and Collaboration Framework. Prior to version 1.7.1, an extension execution path in Faction’s extension f...
  • CVE-2025-66269 – The RupsMon and USBMate services in UPSilon 2000 run with SYSTEM privileges and contain unquoted service paths. This allows a local attacker to per...
  • CVE-2025-66266 – The RupsMon.exe service executable in UPSilon 2000 has insecure permissions, allowing the 'Everyone' group Full Control. A local attacker can repla...