Transaction substitution via incomplete linear-proof validation
Published Nov 23, 2022 · Updated Apr 22, 2025
Proof-verification failure in Codenotary immudb SDKs before 1.4.1 allows remote attackers controlling a server to substitute transaction data. The client validates only the first and last nodes of a consumed linear proof, without proving that intermediate hashes entered the newer Merkle tree. Exploitation requires a malicious server, a linear proof longer than one node, and a specific sequence of verified reads or writes; the accepted false state compromises transaction integrity.
Summary
What happened
Proof-verification failure in Codenotary immudb SDKs before 1.4.1 allows remote attackers controlling a server to substitute transaction data. The client validates only the first and last nodes of a consumed linear proof, without proving that intermediate hashes entered the newer Merkle tree. Exploitation requires a malicious server, a linear proof longer than one node, and a specific sequence of verified reads or writes; the accepted false state compromises transaction integrity.
The record
- CVE
- CVE-2022-36111
- Published
- Nov 23, 2022
- Updated
- Apr 22, 2025
- Vendor
- Codenotary
- Product
- immudb
- Classifications
- CWE-345, T1565.002
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 23, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream linear-fake proof-of-concept serverproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo