Security readout for executives and security teams
Plain-English summary
A flaw in the mJS JavaScript engine can dereference a NULL pointer while printing, which may crash affected software. The business risk is mainly availability for products that embed mJS and run attacker-controlled or untrusted scripts. The available sources do not identify affected versions or a confirmed patch.
Executive priority
Prioritize this as an exposure-discovery item unless mJS is found in internet-facing or safety-critical systems. Escalate remediation if untrusted script input can reach affected code, because availability loss may be operationally meaningful.
Technical view
CVE-2021-33447 is reported as a NULL pointer dereference in mjs_print() in mjs.c in mJS, a restricted JavaScript engine, described against ES6 JavaScript handling. The public bundle provides no CVSS score, CWE mapping, affected version range, or vendor remediation detail.
Likely exposure
Exposure is likely limited to applications, appliances, or embedded systems that include Cesanta mJS and allow JavaScript execution paths that reach mjs_print(). The source bundle lists affected product and version as n/a, so asset confirmation is required.
Exploitation context
The bundle cites a GitHub issue and public gist, but does not cite active exploitation. KEV status is false. Treat public proof details as a signal to validate exposure, not as evidence of observed attacks.
Researcher notes
The record is sparse: no CVSS, CWE, affected versions, or patch status are provided. The core claim is a NULL pointer dereference in mjs_print(). Any severity assessment should be tied to local embedding context and script trust boundaries.
Mitigation direction
- Inventory applications and firmware for Cesanta mJS usage.
- Check the upstream issue and vendor guidance for fixed versions or workarounds.
- Reduce or disable untrusted JavaScript execution where feasible.
- Limit script paths that can invoke printing behavior.
- Monitor affected services for unexpected crashes or restarts.
Validation and detection
- Search SBOMs and dependency records for mJS or cesanta/mjs.
- Confirm whether any exposed workflow executes untrusted JavaScript.
- Map discovered mJS copies to exact upstream versions or commits.
- Review crash logs for failures around mjs_print or script printing.
- Retest affected workflows after applying vendor-recommended updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-33447 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/cesanta/mjs/issues/164CVE reference · x_refsource_MISC
- https://gist.github.com/Clingto/bb632c0c463f4b2c97e4f65f751c5e6dCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.