Client state substitution via unvalidated server UUID
Published Nov 22, 2022 · Updated Apr 23, 2025
Improper server UUID validation in Codenotary immudb before 1.4.1 allows attackers to make clients accept unrelated state. The Go client SDK keys persisted verification state by the UUID supplied by the server without first validating that identity, so a changed UUID creates a separate state context. Control of server responses is required, and the consequence is acceptance of state unrelated to the previously verified server history.
Summary
What happened
Improper server UUID validation in Codenotary immudb before 1.4.1 allows attackers to make clients accept unrelated state. The Go client SDK keys persisted verification state by the UUID supplied by the server without first validating that identity, so a changed UUID creates a separate state context. Control of server responses is required, and the consequence is acceptance of state unrelated to the previously verified server history.
The record
- CVE
- CVE-2022-39199
- Published
- Nov 22, 2022
- Updated
- Apr 23, 2025
- Vendor
- Codenotary
- Product
- immudb
- Classifications
- CWE-345, T1565.002
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Nov 22, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 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
No public exploit references are available in this record.
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