CVE-2015-6764
Buffer Overflow in The BasicJsonStringifier::SerializeJSArray function in json-stringifier
Executive Summary
CVE-2015-6764 is a critical severity vulnerability affecting binary-analysis. It is classified as Memory Buffer Overflow. Ensure your systems and dependencies are patched immediately to mitigate exposure risks.
Precogs AI Insight
"Google Chrome's V8 engine contains an out-of-bounds read/write vulnerability in the `BasicJsonStringifier::SerializeJSArray` function. Attackers provide crafted JSON data to corrupt memory and execute arbitrary code. Precogs Binary Analysis detects unsafe type casting in dynamic compilation."
What is this vulnerability?
CVE-2015-6764 is categorized as a critical Buffer Overflow flaw with a CVSS base score of 9.8. Based on our vulnerability intelligence, this issue occurs when the application fails to securely handle untrusted data boundaries.
The BasicJsonStringifier::SerializeJSArray function in json-stringifier.h in the JSON stringifier in Google V8, as used in Google Chrome before 47.0.2526.73, improperly loads array elements, which allows remote attackers to cause a denial of service (out-of-bounds memory access) or possibly have unspecified other impact via crafted JavaScript code.
This architectural defect enables adversaries to bypass intended security controls, directly manipulating the application's execution state or data layer. Immediate strategic intervention is required.
Risk Assessment
| Metric | Value |
|---|---|
| CVSS Base Score | 9.8 (CRITICAL) |
| Vector String | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Published | December 6, 2015 |
| Last Modified | April 12, 2025 |
| Related CWEs | CWE-119 |
Impact on Systems
✅ Remote Code Execution: Attackers can overwrite the instruction pointer to redirect execution to malicious shellcode.
✅ Memory Corruption: Overwriting adjacent memory regions can corrupt critical application state, leading to privilege escalation.
✅ Denial of Service: Triggering segmentation faults results in immediate disruption of critical systems.
How to Fix and Mitigate CVE-2015-6764
- Apply Vendor Patches: Upgrade affected components to their latest, non-vulnerable versions immediately.
- Implement Input Validation: Ensure all user-supplied data is validated, sanitized, and type-checked before processing.
- Deploy Runtime Protection: Use Precogs continuous monitoring to detect exploitation attempts in real time.
- Audit Dependencies: Review and update all third-party libraries and transitive dependencies.
Defending with Precogs AI
Google Chrome's V8 engine contains an out-of-bounds read/write vulnerability in the BasicJsonStringifier::SerializeJSArray function. Attackers provide crafted JSON data to corrupt memory and execute arbitrary code. Precogs Binary Analysis detects unsafe type casting in dynamic compilation.
Use Precogs to continuously scan your codebase, binaries, APIs, and infrastructure for this vulnerability class and related attack patterns. Our AI-powered detection engine combines static analysis with threat intelligence to identify exploitable weaknesses before attackers do.
Vulnerability Code Signature
Attack Data Flow
| Stage | Detail |
|---|---|
| Source | Network packet or file input |
| Vector | Data exceeds the allocated buffer bounds during a copy operation |
| Sink | strcpy(), memcpy(), or pointer arithmetic |
| Impact | Memory corruption, Remote Code Execution (RCE) |
Vulnerable Code Pattern
// ❌ VULNERABLE: Memory Buffer Overflow
void process_data(char *input) {
char buffer[64];
// Taint sink: copies without bounds checking
strcpy(buffer, input);
}
Secure Code Pattern
// ✅ SECURE: Bounded copy
void process_data(char *input) {
char buffer[64];
// Sanitized boundary check
strncpy(buffer, input, sizeof(buffer) - 1);
buffer[sizeof(buffer) - 1] = '\0';
}
How Precogs Detects This
Precogs Binary SAST engine explicitly uncovers memory boundary violations and unsafe memory management functions in compiled binaries.\n