# CVE-2022-24032: Information disclosure in n/a

> Attackers can enumerate valid usernames on Adenza AxiomSL ControllerView due to inconsistent error messages during failed login attempts.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 30 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v63v-32vm-px2m

## What is CVE-2022-24032?

CVE-2022-24032 is a medium-severity vulnerability in n/a, published on 30 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Adenza AxiomSL ControllerView through 10.8.1 is vulnerable to user enumeration. An attacker can identify valid usernames on the platform because a failed login attempt produces a different error message when the username is valid.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Adenza Axiomsl Controllerview.

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

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

## Is CVE-2022-24032 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-22919](https://insights.sbomify.com/CVE-2022-22919/): Open redirect in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24032 is a medium-severity vulnerability in n/a, published on 30 Jan 2022. 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-2022-24032 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-2022-24032/ (Markdown: https://insights.sbomify.com/CVE-2022-24032/index.md)
```

## Sources

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

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