CVE-2023-36201
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue in JerryscriptProject jerryscript v.3.0.0 allows an attacker to obtain sensitive information via a crafted script to the arrays.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceJerryScript JavaScript engine version 3.0.0 contains an information disclosure vulnerability in its array handling implementation. A specially crafted JavaScript script can trigger the vulnerability to read sensitive data from memory via improper array access. The issue is classified as HIGH severity (CVSS 7.5) due to the potential for confidentiality breach with no user interaction required.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify JerryScript installationSearch for jerry executable, libjerry library files, or jerry.h header in your environment. Check build artifacts, dependencies, or embedded usage.Affected if JerryScript is present in the environment
-
Determine JerryScript versionRun 'jerry --version' or inspect version strings in library binaries, source code headers, or build configuration files.Affected if Version is exactly 3.0.0
-
Confirm array handling is in useReview your JavaScript code or scripts executed by the JerryScript engine for array operations (array creation, indexing, push, pop, iteration).Affected if Scripts using array features are executed by version 3.0.0
You are affected if JerryScript version 3.0.0 is deployed and processes any JavaScript code, as the vulnerability resides in the core array handling implementation and requires no special configuration to be exploitable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to a patched version of JerryScript if available; otherwise, implement strict input validation and sandboxing around script execution to limit the impact of crafted malicious scripts.
Jerryscript 3.1.0 or later stable release (verify exact fixed version in Jerryscript security advisories)
- 1. Check the official Jerryscript GitHub repository (github.com/jerryscript-project/jerryscript) for the latest stable release
- 2. Review the release notes or security advisories to confirm the version that addresses CVE-2023-36201
- 3. Download or clone the fixed version
- 4. Replace the vulnerable jerryscript library/binary with the new version
- 5. Test your application to ensure functionality remains intact after the upgrade
- 6. Re-deploy the updated jerryscript in your environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-36201 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data