# CVE-2022-40798: Auth bypass in n/a

> Attackers can bypass access controls to retrieve real email addresses and take over user accounts in OcoMon.

- **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:** 19 Oct 2022
- **Updated:** 8 May 2025
- **Also known as:** GHSA-73hh-p4j2-j7gj

## What is CVE-2022-40798?

CVE-2022-40798 is a high-severity authentication bypass vulnerability in n/a, published on 19 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OcoMon 4.0RC1 is vulnerable to Incorrect Access Control. Through a request the user can obtain the real email, sending the same request with correct email its possible to account takeover.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Ocomon Project Ocomon.

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

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

## Is CVE-2022-40798 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-41390](https://insights.sbomify.com/CVE-2022-41390/): SQL injection in n/a (critical 9.8)
- [CVE-2022-41391](https://insights.sbomify.com/CVE-2022-41391/): SQL injection in n/a (critical 9.8)
- [CVE-2023-33559](https://insights.sbomify.com/CVE-2023-33559/): Path traversal in n/a (high 8.8)
- [CVE-2023-33558](https://insights.sbomify.com/CVE-2023-33558/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40798 is a high-severity authentication bypass vulnerability in n/a, published on 19 Oct 2022. 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-40798 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-2022-40798/ (Markdown: https://insights.sbomify.com/CVE-2022-40798/index.md)
```

## Sources

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

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