# CVE-2023-2799: cnoa OA hard-coded password

> An attacker can exploit a hard-coded password in the cnoa OA login functionality to gain unauthorized access to user accounts.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2023
- **Updated:** 22 Nov 2024
- **Also known as:** GHSA-vr72-jfg9-pccj

## What is CVE-2023-2799?

CVE-2023-2799 is a medium-severity vulnerability in cnoa OA, published on 18 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability, which was classified as problematic, has been found in cnoa OA up to 5.1.1.5. Affected by this issue is some unknown functionality of the file /index.php?app=main&func=passport&action=login. The manipulation leads to use of hard-coded password. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-229376. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2023-2799?

It affects 1 product.


Products: Cnoa Oa Project Cnoa Oa.

## How do I fix CVE-2023-2799?

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

## Is CVE-2023-2799 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2799 and fix it if it is affected.

What it is: CVE-2023-2799 is a medium-severity vulnerability in cnoa OA, published on 18 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-2799 in the wild and no public exploit code.

Affected product: cnoa OA. 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-2023-2799/ (Markdown: https://insights.sbomify.com/CVE-2023-2799/index.md)
```

## Sources

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

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