json-smart through 2.6.0 contains an input validation bypass vulnerability that allows attackers to evade strict-mode trailing-data checks by inserting a literal 0x1A character. Attackers can append 0x1A and malformed content to pass JSONValue.parseStrict or isValidJsonStrict val...
Product
debian/json-smart vulnerabilities
5 published CVES affecting debian/json-smart, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 0
- High
- 3
- Medium
- 1
- Low
- 0
- Unscored
- 1
- CISA KEV
- 0
Latest debian/json-smart CVEs
Newest publication first
-
MediumCVSS 6.9 EPSS 0.45%
-
HighCVSS 7.5 EPSS 0.58% PoC
A security issue was found in Netplex Json-smart 2.5.0 through 2.5.1. When loading a specially crafted JSON input, containing a large number of ’{’, a stack exhaustion can be trigger, which could allow an attacker to cause a Denial of Service (DoS). This issue exists because of a...
-
DLA-3373-1 json-smart - security update
PublishedUnknown -
CVE-2023-1370 Stack exhaustion in json-smart leads to denial of service when parsing malformed JSON
PublishedHighCVSS 7.5 EPSS 1.1%Json-smart is a performance focused, JSON processor lib. When reaching a ‘[‘ or ‘{‘ character in the JSON input, the code parses an array or an object respectively. It was discovered that the code does not have any limit to the nesting of such arrays or objects. Since the parsing...
-
HighCVSS 7.5 EPSS 2.3%
A vulnerability was discovered in the indexOf function of JSONParserByteArray in JSON Smart versions 1.3 and 2.4 which causes a denial of service (DOS) via a crafted web request.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.