# CVE-2024-55198: Information disclosure in n/a

> Remote attackers can enumerate valid users by analyzing discrepancies in error messages during password recovery in Celk Saude.

- **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:** 13 Mar 2025
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-6rjg-2hv4-xq68

## What is CVE-2024-55198?

CVE-2024-55198 is a medium-severity vulnerability in n/a, published on 13 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

User Enumeration via Discrepancies in Error Messages in the Celk Sistemas Celk Saude v.3.1.252.1 password recovery functionality which allows a remote attacker to enumerate users through discrepancies in the responses.

Weakness: CWE-204 (Observable Response Discrepancy)

## Which versions are affected by CVE-2024-55198?

It affects 1 product.


Products: Celk Celk Saude.

## How do I fix CVE-2024-55198?

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

## Is CVE-2024-55198 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-48761](https://insights.sbomify.com/CVE-2024-48761/): Cross-site scripting in n/a (high 8.8)
- [CVE-2024-51182](https://insights.sbomify.com/CVE-2024-51182/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-55199](https://insights.sbomify.com/CVE-2024-55199/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-55198 and fix it if it is affected.

What it is: CVE-2024-55198 is a medium-severity vulnerability in n/a, published on 13 Mar 2025. 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-2024-55198 exists.

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-2024-55198/ (Markdown: https://insights.sbomify.com/CVE-2024-55198/index.md)
```

## Sources

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

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