Security readout for executives and security teams
Plain-English summary
CVE-2020-28434 is a critical command injection issue in the npm package gitblame. If an application uses this package with untrusted input, an attacker may be able to run unintended system commands. The sources identify all versions as affected, but do not provide a confirmed fixed version.
Executive priority
Treat this as urgent if gitblame exists in production services, CI, or tools processing external input. Business risk is high because successful command injection can compromise host confidentiality and integrity. If gitblame is unused or only in isolated local tooling, urgency may be lower.
Technical view
The CVE describes command injection in gitblame, with the injection point in lib/gitblame.js line 15. CVSS 3.1 score is 9.4, network-accessible, low complexity, no privileges, and no user interaction required. Available sources do not include exploit details or a named patch.
Likely exposure
Exposure is most likely in Node.js projects that directly or transitively depend on gitblame, especially services or automation that pass external repository, path, commit, branch, or user-supplied values into gitblame functionality.
Exploitation context
The source bundle marks CISA KEV as false, so there is no cited evidence of active exploitation here. The CVSS vector indicates proof-of-concept maturity, but the provided sources do not include safe validation details or exploitation telemetry.
Researcher notes
The evidence set is narrow but consistent: CVE and Snyk identify gitblame command injection affecting all versions. Do not assume broader ecosystem impact. Validate dependency presence and reachability before escalation. No offensive payloads, exploit procedure, or confirmed active exploitation are provided in the sources.
Mitigation direction
- Inventory applications and build tooling for direct or transitive gitblame dependency use.
- Check Snyk, CVE, and package maintainer guidance for fixed or replacement versions.
- Remove or replace gitblame where external input can reach it.
- Block untrusted input from reaching gitblame-dependent code paths.
- Prioritize remediation for internet-facing services and CI systems handling external repositories.
Validation and detection
- Search package manifests, lockfiles, and SBOMs for gitblame.
- Use SCA tooling to confirm CVE-2020-28434 or SNYK-JS-GITBLAME-1050430 exposure.
- Review code paths that call gitblame with user-controlled values.
- Confirm whether affected code is reachable in production, CI, or internal tooling.
- Document absence of a cited fixed version before accepting upgrade-based remediation.
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.
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 lookupCVE-2020-28434 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
- Critical
- CVSS
- 9.4 (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:L/E:P/RL:O/RC:C
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:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L/E:P/RL:O/RC:C3.95.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.4CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L/E:P/RL:O/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- https://security.snyk.io/vuln/SNYK-JS-GITBLAME-1050430CVE 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.