Audit-log disclosure via AES-CTR nonce reuse
Published May 17, 2023 · Updated Jan 22, 2025
Inadequate encryption in Dgraph before 23.0.0 allows local users to recover confidential audit-log contents through nonce collisions. The audit log writer builds each AES-CTR nonce from a per-log 12-byte base IV and the four-byte log-line length, so equal-length lines reuse the same keystream. Exploitation requires access to encrypted audit-log files; the reported consequence is disclosure of logged data without database modification or service interruption.
Summary
What happened
Inadequate encryption in Dgraph before 23.0.0 allows local users to recover confidential audit-log contents through nonce collisions. The audit log writer builds each AES-CTR nonce from a per-log 12-byte base IV and the four-byte log-line length, so equal-length lines reuse the same keystream. Exploitation requires access to encrypted audit-log files; the reported consequence is disclosure of logged data without database modification or service interruption.
The record
- CVE
- CVE-2023-31135
- Published
- May 17, 2023
- Updated
- Jan 22, 2025
- Vendor
- Dgraph Labs
- Product
- Dgraph
- Classifications
- CWE-326, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 17, 2023CVE publishedPublication date reported by the CVE source.
- Jan 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=< 23.0.0
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.
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