# CVE-2022-4399: TicklishHoneyBee nodau db.c sql injection

> An attacker can perform SQL injection via the value/name argument in the nodau library, potentially reading or modifying database contents.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-4399, GHSA-6v9c-g7xh-jm8v, UBUNTU-CVE-2022-4399

## What is CVE-2022-4399?

CVE-2022-4399 is a medium-severity SQL injection vulnerability in TicklishHoneyBee nodau, published on 10 Dec 2022. 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 TicklishHoneyBee nodau. It has been rated as critical. Affected by this issue is some unknown functionality of the file src/db.c. The manipulation of the argument value/name leads to sql injection. The name of the patch is 7a7d737a3929f335b9717ddbd31db91151b69ad2. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-215252.

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

## Which versions are affected by CVE-2022-4399?

It affects 1 product.


Products: Nodau Project Nodau.

## How do I fix CVE-2022-4399?

Apply the vendor's patch.

## Is CVE-2022-4399 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4399 and fix it if it is affected.

What it is: CVE-2022-4399 is a medium-severity SQL injection vulnerability in TicklishHoneyBee nodau, published on 10 Dec 2022. 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-2022-4399 in the wild and no public exploit code.

Affected product: TicklishHoneyBee nodau. 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-2022-4399/ (Markdown: https://insights.sbomify.com/CVE-2022-4399/index.md)
```

## Sources

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

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