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

> An attacker can steal NTLM hashes by tricking a user into loading a remote image, potentially leading to computer compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q8gr-rr8w-mwmq

## What is CVE-2020-12772?

CVE-2020-12772 is a high-severity vulnerability in n/a, published on 12 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Ignite Realtime Spark 2.8.3 (and the ROAR plugin for it) on Windows. A chat message can include an IMG element with a SRC attribute referencing an external host's IP address. Upon access to this external host, the (NT)LM hashes of the user are sent with the HTTP request. This allows an attacker to collect these hashes, crack them, and potentially compromise the computer. (ROAR can be configured for automatic access. Also, access can occur if the user clicks.)

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

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

It affects 1 product.


Products: Igniterealtime Spark.

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

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

## Is CVE-2020-12772 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12772 is a high-severity vulnerability in n/a, published on 12 May 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-12772 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-12772/ (Markdown: https://insights.sbomify.com/CVE-2020-12772/index.md)
```

## Sources

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

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