Security readout for executives and security teams
Plain-English summary
Total.js applications using total.js before 3.4.9 may be vulnerable if they pass user-controlled input into utils.set. In that situation, the framework could treat attacker-controlled data as code, potentially allowing arbitrary code execution. The sources name version 3.4.9 as the fix.
Executive priority
Treat this as a high-priority dependency remediation for applications using total.js. Business urgency is highest where total.js services process sensitive data or expose code paths that pass user-influenced values into utils.set. No source in the bundle supports emergency active-exploitation handling.
Technical view
CVE-2021-32831 is CWE-94 code injection in the total.js npm framework. The vulnerable behavior is in utils.set before 3.4.9 when called with user-controlled values. CVSS 3.1 is 7.5 with local attack vector, high complexity, high privileges required, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to Node.js services that depend on the total.js package below 3.4.9 and use utils.set on untrusted or user-influenced values. The source bundle does not identify vulnerable downstream applications, internet-wide exposure, or specific deployment patterns.
Exploitation context
The provided sources do not show active exploitation, and this CVE is not listed as KEV in the bundle. Exploitation requires the vulnerable function to be reachable with user-controlled values and, per CVSS, assumes high privileges, high complexity, and local attack vector.
Researcher notes
Focus assessment on dependency version and reachability of utils.set. The public description ties impact to user-controlled values reaching that function, not every total.js installation. Avoid assuming remote exploitability beyond the CVSS vector and advisory language provided.
Mitigation direction
- Upgrade total.js to version 3.4.9 or later.
- Identify and prioritize applications using total.js below 3.4.9.
- Review code paths calling utils.set with user-controlled values.
- Follow vendor project guidance if additional remediation details are published.
Validation and detection
- Check package-lock, yarn.lock, pnpm-lock, or runtime inventory for total.js versions.
- Search application code for utils.set usage.
- Confirm untrusted input cannot reach utils.set in vulnerable deployments.
- Run existing unit and integration tests after upgrading total.js.
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.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-32831 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
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
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 vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H0.86Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/totaljs/framework/commit/887b0fa9e162ef7a2dd9cec20a5ca122726373b3CVE reference · x_refsource_MISC
- https://securitylab.github.com/advisories/GHSL-2021-066-totaljs-totaljs/CVE reference · x_refsource_CONFIRM
- https://github.com/totaljs/framework/blob/e644167d5378afdc45cb0156190349b2c07ef235/changes.txt#L11CVE reference · x_refsource_MISC
- https://www.npmjs.com/package/total.jsCVE 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.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.