# CVE-2020-36768: rl-institut NESP2 database.py sql injection

> Remote attackers can exploit SQL injection in NESP2 to read or modify database contents, requiring immediate patching.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Dec 2023
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-ch26-w8p4-8q82

## What is CVE-2020-36768?

CVE-2020-36768 is a high-severity SQL injection vulnerability in rl-institut NESP2, published on 3 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in rl-institut NESP2 Initial Release/1.0. It has been classified as critical. Affected is an unknown function of the file app/database.py. The manipulation leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The patch is identified as 07c0cdf36cf6a4345086d07b54423723a496af5e. It is recommended to apply a patch to fix this issue. VDB-246642 is the identifier assigned to this vulnerability.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2020-36768?

It affects 1 product.


Products: Reiner-Lemoine-Institut Nesp2.

## How do I fix CVE-2020-36768?

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

## Is CVE-2020-36768 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36768 and fix it if it is affected.

What it is: CVE-2020-36768 is a high-severity SQL injection vulnerability in rl-institut NESP2, published on 3 Dec 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-2020-36768 in the wild and no public exploit code.

Affected product: rl-institut NESP2. 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-2020-36768/ (Markdown: https://insights.sbomify.com/CVE-2020-36768/index.md)
```

## Sources

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

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