LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23375: Arbitrary Command Injection

This affects all versions of package psnode. If attacker-controlled user input is given to the kill 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.

HighCVSS 7.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-23375 is a command injection issue in the npm package psnode. If an application passes attacker-controlled input into psnode's kill function, that input can be executed as system commands. Business urgency depends on whether psnode is installed and reachable through an exposed workflow.

Executive priority

Prioritize remediation for internet-facing or multi-tenant services using psnode. For internal-only systems, first confirm actual package usage and data flow, then schedule removal or replacement based on reachability and business criticality.

Technical view

The issue affects psnode as described in the source bundle. The vulnerable behavior is use of Node.js child_process exec without sanitizing input in the kill function. CVSS is 7.3 high, with network attack vector and no privileges or user interaction required in the scored scenario.

Likely exposure

Exposure is most likely in Node.js applications that depend on psnode and allow users, API callers, or external systems to influence arguments passed to kill. Systems not using psnode, or using it only with trusted internal values, have lower practical exposure.

Exploitation context

The bundle does not cite active exploitation, and the CVE is not listed as CISA KEV. Exploitation would require a vulnerable application path where attacker-controlled input reaches psnode.kill. No source in the bundle confirms public weaponization or observed attacks.

Researcher notes

The key technical condition is attacker-controlled input reaching kill, where exec is used without sanitization. The source bundle names psnode and links to the relevant repository line, but it does not provide a confirmed patch, CWE mapping, or exploitation evidence.

Mitigation direction

  • Inventory applications and lockfiles for the psnode package.
  • Check current package maintainer or Snyk guidance for fixed versions or deprecation advice.
  • Remove or replace psnode where feasible, especially on exposed services.
  • Ensure attacker-controlled values cannot reach psnode.kill.
  • Use safer process-control APIs that avoid shell command execution.

Validation and detection

  • Search dependency manifests and lockfiles for psnode usage.
  • Trace application calls to psnode.kill and identify input sources.
  • Confirm exposed routes or jobs cannot pass user input into kill.
  • Run approved SCA tooling against Node.js projects.
  • Document compensating controls if immediate removal is not possible.
Prepared
Confidence
high
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-23375 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
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/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
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2021-23375Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/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/apsnode0Listed
Weakness

CWE details

No CWE listed

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