CVE-2022-4399: A vulnerability was found in TicklishHoneyBee nodau

Q: How do I fix CVE-2022-4399?

nodau: upgrade to 0.3.9. Exact commands for each OS are on this page.

Q: Is CVE-2022-4399 being exploited?

CVE-2022-4399 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-4399 affect?

CVE-2022-4399 affects nodau. Severity is medium (CVSS 5.5). 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 t

Q: How urgent is CVE-2022-4399?

Priority 33/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2022-4399 is a medium-severity flaw (CVSS 5.5) affecting nodau. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 44%)
CISA exploited list	No
Weakness	CWE-707, CWE-89
Published	2022-12-10
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: nodau project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-10 22:15 UTCPublished CVE record published
2026-06-17 05:20 UTCUpdated Record last modified

nodau project nodau UPGRADE

Affected: < 0.3.9

Fixed in: 0.3.9

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy nodau || rpm -q nodau || nodau --version

2. UPGRADE to 0.3.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade nodau

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade nodau

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-4399?

nodau: upgrade to 0.3.9. Exact commands for each OS are on this page.

Is CVE-2022-4399 being exploited?

CVE-2022-4399 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-4399 affect?

CVE-2022-4399 affects nodau. Severity is medium (CVSS 5.5). 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 t

How urgent is CVE-2022-4399?

Priority 33/100. No elevated risk signals yet.

References

← Back to latest CVEs