# CVE-2020-17477: Information disclosure in n/a

> Remote users can read LDAP password hashes due to incorrect ACLs, potentially leading to privilege escalation via NTLM hash reuse.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 26 Oct 2023
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-39vr-m637-4v3h

## What is CVE-2020-17477?

CVE-2020-17477 is a medium-severity vulnerability in n/a, published on 26 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Incorrect LDAP ACLs in ucs-school-ldap-acls-master in UCS@school before 4.4v5-errata allow remote teachers, staff, and school administrators to read LDAP password hashes (sambaNTPassword, krb5Key, sambaPasswordHistory, and pwhistory) via LDAP search requests. For example, a teacher can gain administrator access via an NTLM hash.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Univention Ucs\@school.

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

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

## Is CVE-2020-17477 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-17477 is a medium-severity vulnerability in n/a, published on 26 Oct 2023. 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-17477 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-17477/ (Markdown: https://insights.sbomify.com/CVE-2020-17477/index.md)
```

## Sources

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

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