LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23376: Arbitrary Command Injection

This affects all versions of package ffmpegdotjs. If attacker-controlled user input is given to the trimvideo function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2021-23376 is a critical command injection issue in the npm package ffmpegdotjs. If an application passes attacker-controlled input into trimvideo, the package can execute operating system commands. This creates potential full server compromise for affected media-processing services.

Executive priority

Prioritize quickly if ffmpegdotjs is present in internet-facing or customer-upload media services. The business risk is server takeover, data theft, service disruption, or lateral movement from a vulnerable processing host.

Technical view

The issue is tied to ffmpegdotjs using Node.js child_process exec without sanitizing trimvideo input. The CVSS 3.1 score is 9.8, with network attack vector, low complexity, no privileges, and no user interaction. Sources do not identify a fixed version.

Likely exposure

Exposure is likely limited to Node.js applications that use ffmpegdotjs and route untrusted input into trimvideo, such as upload, clipping, or media-processing workflows. Inventory confirmation is required.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The CVSS vector indicates remote, unauthenticated exploitability if vulnerable code paths expose trimvideo to attacker-controlled values.

Researcher notes

Evidence supports command injection through trimvideo input handling and child_process exec usage. The affected package data is sparse, and the sources do not name a patch, workaround, or exploitation in the wild.

Mitigation direction

  • Inventory applications and lockfiles for ffmpegdotjs usage.
  • Do not pass untrusted input to trimvideo.
  • Remove or replace ffmpegdotjs where feasible.
  • Apply strict allowlist validation around media parameters.
  • Run media processing with least privilege and isolation.
  • Check vendor and Snyk guidance for any fixed release.

Validation and detection

  • Confirm whether ffmpegdotjs appears in package manifests or lockfiles.
  • Trace all trimvideo call sites and input sources.
  • Identify public routes or APIs feeding media-processing parameters.
  • Review runtime permissions for affected Node.js services.
  • Check logs for unusual media-processing failures or command errors.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

description · low confidence lookup

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

CVE-2021-23376 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P

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.

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

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2021-23376Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/affmpegdotjs0Listed
Weakness

CWE details

No CWE listed

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