# CVE-2023-3803: Chengdu Flash Flood Disaster Monitoring and Warning System File Name ImageStationDataService.asmx random values

> Attackers can exploit insufficiently random file names in the image service to potentially upload malicious files, requiring high complexity and permissions.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-j5pg-9wf6-gxwr

## What is CVE-2023-3803?

CVE-2023-3803 is a low-severity vulnerability in Chengdu Flash Flood Disaster Monitoring and Warning System, published on 21 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as problematic has been found in Chengdu Flash Flood Disaster Monitoring and Warning System 2.0. This affects an unknown part of the file /Service/ImageStationDataService.asmx of the component File Name Handler. The manipulation leads to insufficiently random values. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-235071. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2023-3803?

It affects 1 product.


Products: Cdwanjiang Flash Flood Disaster Monitoring and Warning System.

## How do I fix CVE-2023-3803?

No fix has been published for CVE-2023-3803 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-3803 being exploited?

There is no known exploitation of CVE-2023-3803 in the wild and no public exploit code.

## Other vulnerabilities in Chengdu Flash Flood Disaster Monitoring and Warning System

- [CVE-2023-3802](https://insights.sbomify.com/CVE-2023-3802/): Chengdu Flash Flood Disaster Monitoring and Warning System Ajaxfileupload.ashx unrestricted upload (medium 5.5)
- [CVE-2023-3804](https://insights.sbomify.com/CVE-2023-3804/): Chengdu Flash Flood Disaster Monitoring and Warning System FileHandler.ashx unrestricted upload (medium 5.5)
- [CVE-2023-3798](https://insights.sbomify.com/CVE-2023-3798/): Chengdu Flash Flood Disaster Monitoring and Warning System upload.aspx unrestricted upload (medium 5.5)
- [CVE-2023-4171](https://insights.sbomify.com/CVE-2023-4171/): Chengdu Flash Flood Disaster Monitoring and Warning System FileDownload.ashx path traversal (medium 4.3)
- [CVE-2023-4172](https://insights.sbomify.com/CVE-2023-4172/): Chengdu Flash Flood Disaster Monitoring and Warning System FileHandler.ashx absolute path traversal (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3803 and fix it if it is affected.

What it is: CVE-2023-3803 is a low-severity vulnerability in Chengdu Flash Flood Disaster Monitoring and Warning System, published on 21 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3803 in the wild and no public exploit code.

Affected product: Chengdu Flash Flood Disaster Monitoring and Warning System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-3803/ (Markdown: https://insights.sbomify.com/CVE-2023-3803/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3803
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3803
- OSV: https://osv.dev/vulnerability/CVE-2023-3803

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-3803/
Summaries are generated and may contain mistakes; the official description above is the record.