# CVE-2020-7032: Avaya WebLM Improper Restriction of XML External Entity Reference


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-q87h-3ppq-wwf5

## What is CVE-2020-7032?

CVE-2020-7032 is a medium-severity vulnerability in Avaya System Manager, published on 13 Nov 2020. 

### Official description

An XML external entity (XXE) vulnerability in Avaya WebLM admin interface allows authenticated users to read arbitrary files or conduct server-side request forgery (SSRF) attacks via a crafted DTD in an XML request. Affected versions of Avaya WebLM include: 7.0 through 7.1.3.6 and 8.0 through 8.1.2.

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

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

It affects 2 products.


Products: Avaya Aura System Manager, Avaya Weblm.

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

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

## Is CVE-2020-7032 being exploited?

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

## Other vulnerabilities in Avaya System Manager

- [CVE-2024-7477](https://insights.sbomify.com/CVE-2024-7477/): Avaya Aura System Manager SQL injection vulnerability (medium 6.5)
- [CVE-2024-7480](https://insights.sbomify.com/CVE-2024-7480/): Improper access control in Avaya Aura System Manager (medium 4.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-7032 is a medium-severity vulnerability in Avaya System Manager, published on 13 Nov 2020. 
Exploitation: There is no known exploitation of CVE-2020-7032 in the wild and no public exploit code.

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

## Sources

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

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