Skip to content
Fencer Vulns
medium 5.4

CVE-2022-36111 json

immundb has insufficient verification of data authenticity

published 2022-11-21 3 y ago modified 2026-06-17 4 mo ago also GHSA-672p-m5jq-mrh8 , GO-2022-1117 , EUVD-2022-7253

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits
0
none known

Summary

immudb is a database with built-in cryptographic proof and verification. In versions prior to 1.4.1, a malicious immudb server can provide a falsified proof that will be accepted by the client SDK signing a falsified transaction replacing the genuine one. This situation can not be triggered by a genuine immudb server and requires the client to perform a specific list of verified operations resulting in acceptance of an invalid state value. This vulnerability only affects immudb client SDKs, the immudb server itself is not affected by this vulnerability. This issue has been patched in version 1.4.1.

Patch / fix

  • go github.com/codenotary/immudb 1.4.1
  • codenotary immudb 1.4.1

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/codenotary/immudb/security/advisories/GHSA-672p-m5jq-mrh8 referenced PoC, tagged "exploit" by a source, unverified
  • github.com https://github.com/codenotary/immudb/tree/master/docs/security/vulnerabilities/linear-fake referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:H/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/codenotary/immudb
<1.4.1
1.4.1

Affected products

  • codenotary immudb

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.