Service crash via lexer out-of-bounds read
Published Oct 19, 2022 · Updated May 8, 2025
Heap-buffer overflow in jsonlint 1.0 allows attackers to crash the command-line validator by processing a crafted JSON file. While scanning a string, ReadString calls PeekCharacter, and ReadCharacter reads one byte past the heap-backed input buffer. Processing the crafted file is required; the demonstrated consequence is an AddressSanitizer abort, with no reported data disclosure or code execution.
Summary
What happened
Heap-buffer overflow in jsonlint 1.0 allows attackers to crash the command-line validator by processing a crafted JSON file. While scanning a string, ReadString calls PeekCharacter, and ReadCharacter reads one byte past the heap-backed input buffer. Processing the crafted file is required; the demonstrated consequence is an AddressSanitizer abort, with no reported data disclosure or code execution.
The record
- CVE
- CVE-2022-42227
- Published
- Oct 19, 2022
- Updated
- May 8, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 19, 2022CVE publishedPublication date reported by the CVE source.
- May 8, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- AFL crash corpus and AddressSanitizer reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo