# CVE-2024-36823: Weak encryption in Ninja Core

> Weak cryptographic algorithm in Ninja Core allows attackers to potentially leak sensitive information.

- **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:** 6 Jun 2024
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-92wp-jghr-hh87

## What is CVE-2024-36823?

CVE-2024-36823 is a high-severity vulnerability in n/a, published on 6 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The encrypt() function of Ninja Core v7.0.0 was discovered to use a weak cryptographic algorithm, leading to a possible leakage of sensitive information.

Weakness: CWE-326 (Inadequate Encryption Strength), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

2 open source packages ship an affected version, including org.ninjaframework:ninja-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.ninjaframework:ninja-core` | Maven | All versions | None |
| `org.ninjaframework:ninja-core` | Maven | All versions | None |

Products: Ninjaframework Ninja.

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

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

## Is CVE-2024-36823 being exploited?

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

Public exploit code:

- Ninja Framework sensitive information leak due to weak encryption (github_poc): https://github.com/JAckLosingHeart/CVE-2024-36823-POC

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36823 is a high-severity vulnerability in n/a, published on 6 Jun 2024. 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-2024-36823 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.ninjaframework:ninja-core (Maven): affected all versions; no fix listed
- org.ninjaframework:ninja-core (Maven): affected all versions; no fix listed

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-36823/ (Markdown: https://insights.sbomify.com/CVE-2024-36823/index.md)
```

## Sources

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

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