# CVE-2020-12684: XML external entity in n/a

> An attacker can exploit weak XML parser configurations in i-net Clear Reports to perform XXE attacks, potentially reading sensitive data or causing denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 15 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p4mm-c49j-fpjh

## What is CVE-2020-12684?

CVE-2020-12684 is a critical vulnerability in n/a, published on 15 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

XXE injection can occur in i-net Clear Reports 2019 19.0.287 (Designer), as used in i-net HelpDesk and other products, when XML input containing a reference to an external entity is processed by a weakly configured XML parser.

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

## Which versions are affected by CVE-2020-12684?

It affects 1 product.


Products: Inetsoftware I-Net Clear Reports.

## How do I fix CVE-2020-12684?

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

## Is CVE-2020-12684 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-28150](https://insights.sbomify.com/CVE-2020-28150/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12684 and fix it if it is affected.

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

## Sources

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

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