# CVE-2020-7036: XXE in Avaya Callback Assist Administration

> An authenticated remote attacker can exploit an XML External Entity vulnerability in Avaya Callback Assist to read sensitive information stored on the system.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-64f2-mh2m-9cj7

## What is CVE-2020-7036?

CVE-2020-7036 is a high-severity vulnerability in Avaya Callback Assist, published on 23 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An XML External Entities (XXE)vulnerability in Callback Assist could allow an authenticated, remote attacker to gain read access to information that is stored on an affected system. The affected versions of Callback Assist includes all 4.0.x versions before 4.7.1.1 Patch 7.

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

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

It affects 1 product.


Products: Avaya Callback Assist.

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

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

## Is CVE-2020-7036 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7036 is a high-severity vulnerability in Avaya Callback Assist, published on 23 Apr 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-7036 in the wild and no public exploit code.

Affected product: Avaya Callback Assist. 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-7036/ (Markdown: https://insights.sbomify.com/CVE-2020-7036/index.md)
```

## Sources

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

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