LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33437: An issue was discovered in mjs (mJS: Restricted JavaScript engine), ES6 (JavaScript version 6).

An issue was discovered in mjs (mJS: Restricted JavaScript engine), ES6 (JavaScript version 6). There are memory leaks in frozen_cb() in mjs.c.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-33437 reports memory leaks in mJS, a restricted JavaScript engine, specifically in frozen_cb() in mjs.c. Business risk depends on whether your software embeds mJS and allows attacker-influenced scripts or inputs. The source bundle does not provide CVSS, affected versions, fixed versions, or downstream products.

Executive priority

Treat this as an exposure-confirmation item first. Escalate if mJS is present in internet-facing, embedded, or untrusted-script processing paths. Without affected versions, CVSS, or a named fix in the bundle, broad emergency response is not source-supported.

Technical view

The CVE describes memory leaks in frozen_cb() within mjs.c for mJS. A memory leak can increase process memory use and may contribute to service degradation or denial of service in exposed runtimes. The public bundle does not establish affected version ranges, root-cause detail, exploitability conditions, or remediation commits.

Likely exposure

Exposure is most likely in applications, firmware, or services that embed Cesanta mJS. The bundle lists no CPEs, versions, or downstream affected products, so teams must confirm dependency presence internally before assigning urgency.

Exploitation context

The bundle does not cite CISA KEV status and does not provide evidence of active exploitation. Public references include a GitHub issue and gist, but the supplied data does not establish weaponized exploitation or real-world abuse.

Researcher notes

Key gaps are affected version range, CWE, CVSS, fix status, and exploitation prerequisites. Analysis should focus on dependency confirmation, code-path reachability, and whether attacker-controlled input can trigger repeated memory allocation without release.

Mitigation direction

  • Inventory products and repositories for embedded or vendored mJS code.
  • Check the mJS project issue and vendor guidance for fixed commits or releases.
  • Prioritize systems where mJS handles untrusted or remote-controlled script input.
  • Apply available upstream fixes after compatibility testing.
  • Add memory monitoring or restart safeguards where immediate patching is unavailable.

Validation and detection

  • Confirm whether mJS exists in application, firmware, or third-party dependency trees.
  • Review mJS version or commit against upstream issue guidance.
  • Check whether frozen_cb() exists in deployed mjs.c copies.
  • Assess whether untrusted users can influence scripts processed by mJS.
  • Run controlled memory regression testing after any update.
Prepared
Confidence
low
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2021-33437 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.