# CVE-2018-8819: XML external entity in n/a

> Unauthenticated attackers can exploit weak XML parsing to disclose full file contents from the underlying web server OS via the X-Wap-Profile header.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gmgf-pqhp-6w55

## What is CVE-2018-8819?

CVE-2018-8819 is a high-severity vulnerability in n/a, published on 14 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An XXE issue was discovered in Automated Logic Corporation (ALC) WebCTRL Versions 6.0, 6.1 and 6.5. An unauthenticated attacker could enter malicious input to WebCTRL and a weakly configured XML parser will allow the application to disclose full file contents from the underlying web server OS via the "X-Wap-Profile" HTTP header.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2018-8819?

It affects 1 product.


Products: Carrier Automatedlogic Webctrl.

## How do I fix CVE-2018-8819?

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

## Is CVE-2018-8819 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8819 and fix it if it is affected.

What it is: CVE-2018-8819 is a high-severity vulnerability in n/a, published on 14 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-8819 in the wild and no public exploit code.

Affected product: n/a. 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-2018-8819/ (Markdown: https://insights.sbomify.com/CVE-2018-8819/index.md)
```

## Sources

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

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