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

> Attackers can enumerate valid user accounts by analyzing responses from the forgot password feature in FOSS-Online.

- **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:** 12 Sep 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-3qv6-5f5f-f89j

## What is CVE-2024-34336?

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

### Official description

User enumeration vulnerability in ORDAT FOSS-Online before v2.24.01 allows attackers to determine if an account exists in the application by comparing the server responses of the forgot password functionality.

Weakness: CWE-203 (Observable Discrepancy), CWE-204 (Observable Response Discrepancy)

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

It affects 1 product.


Products: Ordat Ordat.erp.

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

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

## Is CVE-2024-34336 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-34334](https://insights.sbomify.com/CVE-2024-34334/): SQL injection in n/a (critical 9.3)
- [CVE-2024-34335](https://insights.sbomify.com/CVE-2024-34335/): ORDAT FOSS-Online before version 2.24.01 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the login page. (medium 6.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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