LiveActive security incident?Get immediate response
CVE Record

CVE-2021-23399: Arbitrary Command Injection

This affects all versions of package wincred. If attacker-controlled user input is given to the getCredential 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-23399 is a command injection flaw in the npm package wincred. If an application sends attacker-controlled input into getCredential, that input can be executed as operating system commands. Business risk depends on whether wincred is present and reachable through user-facing or automated workflows.

Executive priority

Prioritize systems where wincred is used in production and exposed to external or partner-controlled input. This is high severity because successful exploitation can execute commands, but urgency should be driven by reachability and absence of a confirmed patch path.

Technical view

The issue is caused by wincred using child_process exec without sanitizing input passed to getCredential. The CVSS 3.1 score is 7.3 high, with network attack vector, low complexity, no privileges, and no user interaction. The bundle lists all versions as affected, but does not name a patched version.

Likely exposure

Most exposed systems are Node.js applications that include wincred and pass web, API, job, or integration input into getCredential. Internal-only use with fixed credential names is lower risk, but still warrants review because command execution is the impact.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitability is described as possible when attacker-controlled input reaches getCredential. Treat exploit status as unconfirmed, not absent.

Researcher notes

Key evidence is the reported unsanitized exec sink in getCredential and the referenced GitHub source line. The bundle provides no CWE, no KEV evidence, and no confirmed fixed release. Validate data flow rather than relying only on package presence.

Mitigation direction

  • Inventory applications and lockfiles for the wincred package.
  • Review every getCredential call for attacker-controlled input.
  • Remove or replace wincred where untrusted input can reach it.
  • Check Snyk and upstream vendor guidance for any maintained fix.
  • Block untrusted credential-name values before reaching wincred.

Validation and detection

  • Confirm whether wincred is installed in production builds.
  • Map all routes, APIs, jobs, and integrations calling getCredential.
  • Verify getCredential arguments are constant or strictly allowlisted.
  • Check dependency scanners for CVE-2021-23399 findings.
  • Document compensating controls if immediate replacement is not possible.
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-23399 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-23399Attack 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/awincred0Listed
Weakness

CWE details

No CWE listed

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