# CVE-2023-34196: Auth bypass in n/a

> Unauthenticated users can cause partial denial of service and potentially disclose CA certificate attributes in OAuth configurations.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2023
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-hxcm-7rgp-cmh6

## What is CVE-2023-34196?

CVE-2023-34196 is a high-severity authentication bypass vulnerability in n/a, published on 3 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Keyfactor EJBCA before 8.0.0, the RA web certificate distribution servlet /ejbca/ra/cert allows partial denial of service due to an authentication issue. In configurations using OAuth, disclosure of CA certificates (attributes and public keys) to unauthenticated or less privileged users may occur.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Keyfactor Ejbca.

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

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

## Is CVE-2023-34196 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-36066](https://insights.sbomify.com/CVE-2024-36066/): Weak cryptography in n/a (low 3.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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