LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25083: The pullit package before 1.4.0 for Node.js allows OS Command Injection because eval is used on an attacker...

The pullit package before 1.4.0 for Node.js allows OS Command Injection because eval is used on an attacker-supplied Git branch name.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2018-25083 affects the Node.js pullit package before 1.4.0. A malicious Git branch name could be treated as executable input, potentially letting an attacker run operating-system commands in the affected process context.

Executive priority

Treat as urgent only where pullit is present. Prioritize CI, deployment, and repository automation first because successful exploitation could compromise code, secrets, or host integrity.

Technical view

The issue is reported as CWE-78 OS command injection caused by use of eval on an attacker-supplied Git branch name in pullit before 1.4.0. CVSS 3.1 is 9.8, reflecting network reachability, low complexity, no privileges, no user interaction, and high impact.

Likely exposure

Exposure is limited to environments that use the npm pullit package before 1.4.0. Risk is higher where pullit processes branch names from untrusted repositories, users, automation, or CI workflows.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The vulnerability is still serious because the reported primitive is command execution if attacker-controlled branch names reach the vulnerable path.

Researcher notes

The public metadata names pullit before 1.4.0 and references a fixing commit, but affected CPE details are not provided. Do not broaden scope beyond pullit without local dependency evidence.

Mitigation direction

  • Inventory applications and build tooling for pullit usage.
  • Upgrade pullit to 1.4.0 or later where present.
  • Check vendor and package advisory guidance before relying on alternative mitigations.
  • Restrict untrusted branch names from reaching affected automation until remediated.
  • Rebuild and redeploy affected services after dependency updates.

Validation and detection

  • Review package manifests and lockfiles for pullit.
  • Confirm no deployed artifact includes pullit before 1.4.0.
  • Trace whether pullit receives branch names from untrusted sources.
  • Run dependency scanning after remediation.
  • Review CI and automation logs for suspicious pullit-related failures.
Prepared
Confidence
high
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.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter 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 lookup
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-2018-25083 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

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:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2018-25083Attack 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

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

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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