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

> Remote attackers can capture Domain Administrator Net-NTLM hashes by triggering a specific Kerberos event, potentially leading to account takeover.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pfr7-2ph8-36r9

## What is CVE-2020-15931?

CVE-2020-15931 is a high-severity vulnerability in n/a, published on 20 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Netwrix Account Lockout Examiner before 5.1 allows remote attackers to capture the Net-NTLMv1/v2 authentication challenge hash of the Domain Administrator (that is configured within the product in its installation state) by generating a single Kerberos Pre-Authentication Failed (ID 4771) event on a Domain Controller.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Netwrix Account Lockout Examiner.

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

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

## Is CVE-2020-15931 being exploited?

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

Public exploit code:

- Netwrix Account Lockout Examiner 4.1 Domain Admin Account Credential Disclosure Vulnerability (github_poc): https://github.com/optiv/CVE-2020-15931

## Fix prompt for AI coding agents

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

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

## Sources

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

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