CVE-2023-36201
High · 7.5CVSS
7.5
EPSS
0.6%
Published
Jul 7, 2023
CISA due date
—
Cloudanix analysis
A flaw in a JavaScript engine can let attackers steal private information by running a specially made script.
- Exploitation
- Remote Unauthenticated
- Attacker needs
- None
- Complexity
- Low
- Impact
- Data Exposure
- Component
- Library
- Class
- Information Disclosure
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
The vulnerability permits extraction of sensitive data from memory or internal structures by submitting a specially crafted script that exploits improper handling of arrays within the JavaScript engine.
Why it matters to the business
Applications relying on the affected engine risk exposure of confidential information, potentially resulting in data breaches, regulatory penalties, and loss of customer trust; the issue remains unpatched in listed versions with stable low exploit probability.
How an attack unfolds
An attacker identifies a network-accessible instance running the vulnerable engine, crafts a malicious JavaScript payload targeting array operations to trigger unintended data leakage, and retrieves the exposed sensitive information without authentication.
How to fix it
Upgrade Jerryscript to the latest available version addressing array handling issues; if no fixed release exists, implement strict input validation, sandbox execution, or replace the engine with a maintained alternative.
How to confirm the fix worked
Review engine source or test harnesses with array-focused scripts to confirm absence of unintended data exposure; monitor for updates from the project repository.
Typical attack path
- Locate exposed Jerryscript-based service or application
- Develop and deliver crafted script exploiting array handling
- Trigger execution to induce information disclosure
- Capture and exfiltrate sensitive data from response or side effects
How to detect it
Inspect application or engine logs for execution of unexpected or malformed scripts; review network traffic for anomalous payloads targeting array operations; correlate with any observed data leakage events.
What your security team should do
- Prioritize isolating or removing internet-facing instances of the engine
- Track project releases for patches addressing information disclosure
- Apply network segmentation and input sanitization as interim controls
- Audit dependent applications for exposure of sensitive data
The record
An issue in JerryscriptProject jerryscript v.3.0.0 allows an attacker to obtain sensitive information via a crafted script to the arrays.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Ubuntu:18.04:LTS | iotjs | 0 | No fix |
| Ubuntu:22.04:LTS | iotjs | 0 | No fix |
| Ubuntu:Pro:18.04:LTS | iotjs | 0 | No fix |
Related vulnerabilities
- CVE-2024-33255 Jerryscript commit cefd391 was discovered to contain an Assertion Failure via… Also affects iotjs
- CVE-2024-33260 Jerryscript commit cefd391 was discovered to contain a segmentation violation via the… Also affects iotjs
- CVE-2024-33258 Jerryscript commit ff9ff8f was discovered to contain a segmentation violation via the… Also affects iotjs
- CVE-2024-33259 Jerryscript commit cefd391 was discovered to contain a segmentation violation via the… Also affects iotjs
- CVE-2023-36109 Buffer Overflow vulnerability in JerryScript version 3.0, allows remote attackers to… Also affects iotjs
- CVE-2023-38961 Buffer Overflwo vulnerability in JerryScript Project jerryscript v.3.0.0 allows a remote… Also affects iotjs
- CVE-2023-34867 Jerryscript 3.0 (commit 05dbbd1) was discovered to contain an Assertion Failure via the… Also affects iotjs
- CVE-2023-34868 Jerryscript 3.0 (commit 05dbbd1) was discovered to contain an Assertion Failure via the… Also affects iotjs