binary-parser before 2.3.1 Code Injection via String-Typed Parser Options
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| keichi | binary-parser | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | binary-parser before 2.3.1 contains a code injection vulnerability that allows attackers controlling parser definitions to inject JavaScript through string-typed options passed unvalidated by Context.generateOption(). Attackers can supply crafted length, lengthInBytes, key, tag, offset, or namely() alias values to execute arbitrary JavaScript in the Node.js process when the parser is compiled. | |
| Title | binary-parser before 2.3.1 Code Injection via String-Typed Parser Options | |
| First Time appeared |
Keichi
Keichi binary-parser |
|
| Weaknesses | CWE-94 | |
| CPEs | cpe:2.3:a:keichi:binary-parser:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Keichi
Keichi binary-parser |
|
| References |
|
|
| Metrics |
cvssV3_1
|