# CVE-2017-6323: XML external entity in ITMS

> Attackers can exploit weak XML parsing in Symantec ITMS to disclose data, cause denial of service, or perform SSRF.

- **Severity:** High 8.0 (`CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 16 Apr 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-ph8x-8q5q-f3mh

## What is CVE-2017-6323?

CVE-2017-6323 is a high-severity vulnerability in Symantec Corporation ITMS, published on 16 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Symantec Management Console prior to ITMS 8.1 RU1, ITMS 8.0_POST_HF6, and ITMS 7.6_POST_HF7 has an issue whereby XML input containing a reference to an external entity is processed by a weakly configured XML parser. This attack may lead to the disclosure of confidential data, denial of service, server side request forgery, port scanning from the perspective of the machine where the parser is located, and other system impacts.

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

## Which versions are affected by CVE-2017-6323?

It affects 1 product.


Products: Symantec Management Console.

## How do I fix CVE-2017-6323?

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

## Is CVE-2017-6323 being exploited?

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

## Other vulnerabilities in Symantec Corporation ITMS

- [CVE-2017-15527](https://insights.sbomify.com/CVE-2017-15527/): Path traversal in Symantec Management Console (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6323 and fix it if it is affected.

What it is: CVE-2017-6323 is a high-severity vulnerability in Symantec Corporation ITMS, published on 16 Apr 2018. 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-2017-6323 in the wild and no public exploit code.

Affected product: Symantec Corporation ITMS. 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-2017-6323/ (Markdown: https://insights.sbomify.com/CVE-2017-6323/index.md)
```

## Sources

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

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