A path traversal vulnerability exists in the Dahua Smart Park Integrated Management Platform (also referred to as the Dahua Smart Campus Integrated Management Platform), affecting the SOAP-based GIS bitmap upload interface. The flaw allows unauthenticated remote attackers to upload arbitrary files to the server via crafted SOAP requests, including executable JSP payloads. Successful exploitation may lead to remote code execution (RCE) and full compromise of the affected system. The vulnerability is presumed to affect builds released prior to September 2023 and is said to be remediated in newer versions of the product, though the exact affected range remains undefined. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-02-15 UTC.
Security readout for executives and security teams
Plain-English summary
This flaw can let an unauthenticated remote attacker upload arbitrary files to a Dahua Smart Park or Smart Campus management server. The source bundle says executable JSP files may be uploaded, which can lead to remote code execution and full system compromise.
Executive priority
Prioritize this as critical for any exposed Dahua management platform. The combination of unauthenticated remote access, file upload, and potential code execution creates a credible full-compromise path.
Technical view
The issue combines path traversal and unrestricted file upload in a SOAP-based GIS bitmap upload interface. A crafted request may place attacker-controlled files on the server. The exact affected version range is undefined, but the bundle says builds before September 2023 are presumed affected and newer versions are remediated.
Likely exposure
Organizations using Dahua Smart Park Integrated Management Platform, also described as Smart Campus Integrated Management Platform, are the relevant exposure group. Risk is highest when the management platform or its SOAP upload interface is reachable from untrusted networks.
Exploitation context
The bundle does not list this CVE in KEV. It reports Shadowserver observed exploitation evidence on 2024-02-15 UTC, and includes public exploit-oriented references. Treat internet-exposed instances as urgent until verified remediated.
Researcher notes
Evidence is strong for vulnerability class and impact, but incomplete for exact affected versions. Avoid assuming all Dahua products are affected; scope validation to the named Smart Park or Smart Campus integrated management platform.
Mitigation direction
Upgrade to a vendor-remediated Dahua platform release if this product is deployed.
Restrict platform access to VPN or trusted administrative networks.
Block or tightly monitor the SOAP GIS bitmap upload interface where feasible.
Review vendor guidance because the exact affected version range is incomplete.
If compromise is suspected, remove unauthorized files and rotate affected credentials.
Validation and detection
Inventory Dahua Smart Park or Smart Campus management platform deployments.
Confirm product build date and installed version against Dahua guidance.
Check whether the management interface is reachable from the internet.
Review server logs for suspicious SOAP bitmap upload activity.
Inspect web-accessible directories for unexpected uploaded executable files.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.