# CVE-2017-3208: XML external entity in n/a

> An attacker can exploit XML external entity references in AMF3 messages to read sensitive data or cause denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q723-3768-2877

## What is CVE-2017-3208?

CVE-2017-3208 is a critical vulnerability in n/a, published on 11 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Java implementation of AMF3 deserializers used by WebORB for Java by Midnight Coders, version 5.1.1.0, allows external entity references (XXEs) from XML documents embedded within AMF3 messages. If the XML parsing is handled incorrectly it could potentially expose sensitive data on the server, denial of service, or server side request forgery.

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

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

It affects 1 product.


Products: Themidnightcoders Weborb for Java.

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

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

## Is CVE-2017-3208 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-3207](https://insights.sbomify.com/CVE-2017-3207/): Deserialization in WebORB for Java (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3208 is a critical vulnerability in n/a, published on 11 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-2017-3208 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-2017-3208/ (Markdown: https://insights.sbomify.com/CVE-2017-3208/index.md)
```

## Sources

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

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