# CVE-2020-9330: Missing authorization in n/a

> Attackers can change LDAP settings without re-authentication, causing the printer to leak Active Directory credentials to a malicious server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hmxq-86pg-vvrh

## What is CVE-2020-9330?

CVE-2020-9330 is a high-severity missing authorization vulnerability in n/a, published on 21 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Certain Xerox WorkCentre printers before 073.xxx.000.02300 do not require the user to reenter or validate LDAP bind credentials when changing the LDAP connector IP address. A malicious actor who gains access to affected devices (e.g., by using default credentials) can change the LDAP connection IP address to a system owned by the actor without knowledge of the LDAP bind credentials. After changing the LDAP connection IP address, subsequent authentication attempts will result in the printer sending plaintext LDAP (Active Directory) credentials to the actor. Although the credentials may belong to a non-privileged user, organizations frequently use privileged service accounts to bind to Active Directory. The attacker gains a foothold on the Active Directory domain at a minimum, and may use the credentials to take over control of the Active Directory domain. This affects 3655*, 3655i*, 58XX*, 58XXi*, 59XX*, 59XXi*, 6655**, 6655i**, 72XX*, 72XXi*, 78XX**, 78XXi**, 7970**, 7970i**, EC7836**, and EC7856** devices.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 18 products.


Products: Xerox Workcentre 3655 Firmware, Xerox Workcentre 3655i Firmware, Xerox Workcentre 5845 Firmware, Xerox Workcentre 5855 Firmware, Xerox Workcentre 5945 Firmware, Xerox Workcentre 5955 Firmware, Xerox Workcentre 6655 Firmware, Xerox Workcentre 6655i Firmware, Xerox Workcentre 7220 Firmware, Xerox Workcentre 7225 Firmware, Xerox Workcentre 7830 Firmware, Xerox Workcentre 7835 Firmware, Xerox Workcentre 7845 Firmware, Xerox Workcentre 7855 Firmware, Xerox Workcentre 7970 Firmware, Xerox Workcentre 7970i Firmware, Xerox Workcentre Ec7836 Firmware, Xerox Workcentre Ec7856 Firmware.

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

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

## Is CVE-2020-9330 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-11061](https://insights.sbomify.com/CVE-2016-11061/): Command injection in n/a (critical 9.8)
- [CVE-2018-20768](https://insights.sbomify.com/CVE-2018-20768/): Code injection in n/a (critical 9.8)
- [CVE-2018-20770](https://insights.sbomify.com/CVE-2018-20770/): SQL injection in n/a (critical 9.8)
- [CVE-2018-20771](https://insights.sbomify.com/CVE-2018-20771/): Command injection in n/a (critical 9.8)
- [CVE-2018-20767](https://insights.sbomify.com/CVE-2018-20767/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9330 is a high-severity missing authorization vulnerability in n/a, published on 21 Feb 2020. 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-9330 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-9330/ (Markdown: https://insights.sbomify.com/CVE-2020-9330/index.md)
```

## Sources

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

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