# CVE-2019-18380: Auth bypass in Industrial Control System Protection (ICSP)

> Attackers can bypass authentication to create or modify user accounts in Symantec ICSP, potentially gaining unauthorized control over industrial systems.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r93h-8m5r-m5qw

## What is CVE-2019-18380?

CVE-2019-18380 is a medium-severity authentication bypass vulnerability in Symantec Corporation Industrial Control System Protection (ICSP), published on 9 Dec 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Symantec Industrial Control System Protection (ICSP), versions 6.x.x, may be susceptible to an unauthorized access issue that could potentially allow a threat actor to create or modify application user accounts without proper authentication.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-18380?

It affects 1 product.


Products: Symantec Industrial Control System Protection.

## How do I fix CVE-2019-18380?

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

## Is CVE-2019-18380 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18380 and fix it if it is affected.

What it is: CVE-2019-18380 is a medium-severity authentication bypass vulnerability in Symantec Corporation Industrial Control System Protection (ICSP), published on 9 Dec 2019. 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-2019-18380 in the wild and no public exploit code.

Affected product: Symantec Corporation Industrial Control System Protection (ICSP). 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-2019-18380/ (Markdown: https://insights.sbomify.com/CVE-2019-18380/index.md)
```

## Sources

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

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