CVE-2023-1370 (High) detected in json-smart-2.4.8.jar - autoclosed
mend-for-github-com opened this issue · 1 comments
CVE-2023-1370 - High Severity Vulnerability
Vulnerable Library - json-smart-2.4.8.jar
JSON (JavaScript Object Notation) is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language, Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.
Library home page: https://urielch.github.io/
Path to dependency file: /symphony-bdk-test/symphony-bdk-test-spring-boot/build.gradle
Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/net.minidev/json-smart/2.4.8/7c62f5f72ab05eb54d40e2abf0360a2fe9ea477f/json-smart-2.4.8.jar
Dependency Hierarchy:
- symphony-bdk-bom-2.12.0-SNAPSHOT (Root Library)
- spring-boot-dependencies-2.7.9.pom
- ❌ json-smart-2.4.8.jar (Vulnerable Library)
- spring-boot-dependencies-2.7.9.pom
Found in HEAD commit: 0c8fd1d2cd61e6f822378d79406b3c6c6db83073
Found in base branch: main
Vulnerability Details
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 of nested arrays and objects is done recursively, nesting too many of them can cause a stack exhaustion (stack overflow) and crash the software.
Publish Date: 2023-03-22
URL: CVE-2023-1370
CVSS 3 Score Details (7.5)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.