# CVE-2021-38431: Advantech WebAccess SCADA

> Authenticated users can exploit API functions to disclose project names and paths from other users in Advantech WebAccess SCADA.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2021
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pvmh-mh74-89p6

## What is CVE-2021-38431?

CVE-2021-38431 is a medium-severity vulnerability in Advantech WebAccess SCADA, published on 15 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An authenticated user using Advantech WebAccess SCADA in versions 9.0.3 and prior can use API functions to disclose project names and paths from other users.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2021-38431?

It affects 1 product.


Products: Advantech Webaccess Scada.

## How do I fix CVE-2021-38431?

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

## Is CVE-2021-38431 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-38431 and fix it if it is affected.

What it is: CVE-2021-38431 is a medium-severity vulnerability in Advantech WebAccess SCADA, published on 15 Oct 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-38431 in the wild and no public exploit code.

Affected product: Advantech WebAccess SCADA. 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-2021-38431/ (Markdown: https://insights.sbomify.com/CVE-2021-38431/index.md)
```

## Sources

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

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