Summary
Dgraph Audit Log Encryption Vulnerability
Workarounds
Store existing audit logs in a secure location. For extra security, encrypt using a tool like gpg.
References
See https://github.com/dgraph-io/dgraph/pull/8323 for more context on the vulnerability.
Impact
Existing Dgraph audit logs are vulnerable to brute force attacks due to nonce collisions. All audit logs generated by versions of Dgraph <v23.0.0 are affected.
CVE-2023-31135 has a CVSS score of 5.5 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (23.0.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This issue was patched in https://github.com/dgraph-io/dgraph/pull/8323. Dgraph users should upgrade to v23.0.0.
Frequently Asked Questions
- What is CVE-2023-31135? CVE-2023-31135 is a medium-severity security vulnerability in github.com/dgraph-io/dgraph (go), affecting versions < 23.0.0. It is fixed in 23.0.0.
- How severe is CVE-2023-31135? CVE-2023-31135 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/dgraph-io/dgraph are affected by CVE-2023-31135? github.com/dgraph-io/dgraph (go) versions < 23.0.0 is affected.
- Is there a fix for CVE-2023-31135? Yes. CVE-2023-31135 is fixed in 23.0.0. Upgrade to this version or later.
- Is CVE-2023-31135 exploitable, and should I be worried? Whether CVE-2023-31135 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2023-31135 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2023-31135? Upgrade
github.com/dgraph-io/dgraphto 23.0.0 or later.