vault-java-driver: stored deeply nested JSON kills every thread that reads it
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| jopenlibs | vault-java-driver | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Jopenlibs | Vault-java-driver |
|
Vendor Solution
Upgrade io.github.jopenlibs:vault-java-driver to 7.0.0 or later.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.327% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jopenlibs
Jopenlibs vault-java-driver |
|
| Vendors & Products |
Jopenlibs
Jopenlibs vault-java-driver |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | vault-java-driver, a Java client for HashiCorp Vault, parses Vault's JSON responses with a vendored minimal-json parser that has no nesting depth limit. A deeply nested value raises a StackOverflowError, which escapes catch (Exception) handlers and kills the reading thread. A Vault token that can write but not read a KV v2 path can store such a value there, so every later read of that path through the driver fails. This requires Vault 1.19.x or earlier, because 1.20 and later reject values nested deeper than 298 levels. This issue affects io.github.jopenlibs:vault-java-driver 5.2.0 through 6.2.3 and is fixed in 7.0.0. | |
| Title | vault-java-driver: stored deeply nested JSON kills every thread that reads it | |
| Weaknesses | CWE-674 | |
| References |
| |
| Metrics |
cvssV3_1
|