json-smart is vulnerable to Validation Bypass
69
CVE Score
Medium
Validation Bypass
json-smart stores 0x1A as its end of input character, so that same character in a document ends the value early. Strict parsers (JSONValue.parseStrict, JSONValue.isValidJsonStrict, MODE_RFC4627, and MODE_STRICTEST) then accept the truncated value and drop the rest of the input. Untrusted JSON can pass that check while a later parser such as Jackson or Gson keeps the trailing bytes, leading to a parser differential. The fix checks whether the input backend has actually reached the end before it accepts the document.
Upgrade the net.minidev:json-smart library to the patch version.
You are affected if you are using a version that falls within the vulnerable range and you parse untrusted JSON in strict mode.
1.1 - 2.6.0
Fixed in 2.6.1json-smart is vulnerable to Validation Bypass in versions 1.1 - 2.6.0.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.