# CVE-2022-45124: Information disclosure in KingHistorian

> An attacker can sniff network traffic to disclose sensitive information from WellinTech KingHistorian authentication functionality.

- **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 Mar 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xm38-cjvm-pwwc

## What is CVE-2022-45124?

CVE-2022-45124 is a high-severity vulnerability in WellinTech KingHistorian, published on 20 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An information disclosure vulnerability exists in the User authentication functionality of WellinTech KingHistorian 35.01.00.05. A specially crafted network packet can lead to a disclosure of sensitive information. An attacker can sniff network traffic to leverage this vulnerability.

Weakness: CWE-287 (Improper Authentication), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-45124?

It affects 1 product.


Products: Wellintech Kinghistorian.

## How do I fix CVE-2022-45124?

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

## Is CVE-2022-45124 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45124 exists.

## Other vulnerabilities in WellinTech KingHistorian

- [CVE-2012-2559](https://insights.sbomify.com/CVE-2012-2559/): Memory corruption in n/a (critical 10.0)
- [CVE-2022-43663](https://insights.sbomify.com/CVE-2022-43663/): Integer overflow in KingHistorian (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45124 and fix it if it is affected.

What it is: CVE-2022-45124 is a high-severity vulnerability in WellinTech KingHistorian, published on 20 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45124 exists.

Affected product: WellinTech KingHistorian. 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-2022-45124/ (Markdown: https://insights.sbomify.com/CVE-2022-45124/index.md)
```

## Sources

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

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