# CVE-2023-2418: Konga Login API random values

> Attackers can exploit insufficiently random values in the Konga Login API to potentially bypass security controls, requiring configuration changes.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 29 Apr 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9g4c-xm3g-f8hq

## What is CVE-2023-2418?

CVE-2023-2418 is a low-severity vulnerability in Konga, published on 29 Apr 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in Konga 2.8.3 on Kong. It has been classified as problematic. This affects an unknown part of the component Login API. The manipulation leads to insufficiently random values. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to change the configuration settings. The associated identifier of this vulnerability is VDB-227715.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Konghq Kong.

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

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

## Is CVE-2023-2418 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-2418 is a low-severity vulnerability in Konga, published on 29 Apr 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-2418 in the wild and no public exploit code.

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

## Sources

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

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