dbcve.org
JscoverApplication · Jscover Project

CVE-2020-7623

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-02
Fix available
A fix is available. Upgrade to after 1.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
jscover through 1.0.0 is vulnerable to Command Injection. It allows execution of arbitrary command via the source argument.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

jscover through version 1.0.0 contains a command injection vulnerability where the source argument is not properly sanitized before being passed to system commands, allowing an attacker to execute arbitrary commands on the host system.

MitigationImplement strict input validation and sanitization on the source argument, avoiding direct use of user input in system calls; if available, update to a patched version of jscover.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JscoverApplication
Affected:<= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify jscover installation and version
    Run 'npm list jscover' or check package.json for jscover dependency version. If installed globally, use 'npm list -g jscover'
    Affected if The installed version is 1.0.0 or any version <= 1.0.0 (e.g., no version number listed indicates the latest which is 1.0.0)
  2. Locate jscover executable or API usage
    Search for jscover in node_modules/.bin/ or identify scripts that invoke jscover via API (require('jscover')). Check any build scripts or test runners that call jscover
    Affected if jscover is installed and being used in any capacity
  3. Examine how the source argument is provided
    Review the code that invokes jscover - look for arguments passed to jscover, particularly the source/sourceDir parameter. Trace back where that value originates (user input, file, environment variable, hardcoded)
    Affected if The source argument comes from any untrusted or dynamic input such as user parameters, HTTP requests, or unsanitized file contents
  4. Assess command execution context
    Identify if jscover is invoked via child_process.exec, child_process.execSync, or similar system call mechanisms. Check if shell=True or shell execution is used
    Affected if jscover is executed through system command invocation where shell interpretation occurs

You are affected if jscover version 1.0.0 or lower is installed AND the source argument passed to jscover can be influenced by untrusted input without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.0.0
Interim mitigation

Implement strict input validation and sanitization on the source argument, avoiding direct use of user input in system calls; if available, update to a patched version of jscover.

Recommended fix Moderate confidence

jscover@latest (version higher than 1.0.0)

  1. 1. Identify all instances of jscover version 1.0.0 or lower in your project dependencies
  2. 2. Check your package.json or package-lock.json for jscover dependency
  3. 3. Update jscover to the latest available version using: npm install jscover@latest
  4. 4. Verify the upgrade by running: npm list jscover
  5. 5. Test that your code coverage functionality still works as expected after the upgrade
  6. 6. Re-scan the application with security tooling to confirm the vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jscover Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7623 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-7623 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data