Headless Browser LiteApplication · Headless Browser Lite Project

CVE-2016-10625

HIGH · 8.1 CVSS v3.0 Published 2018-06-01
Fix available
A fix is available. Upgrade to 2015.4.18-a or later.
See remediation →
90/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
headless-browser-lite is a minimal npm installer for phantomjs and slimerjs with no external dependencies. headless-browser-lite downloads binary resources over HTTP, which leaves it vulnerable to MITM attacks. It may be possible to cause remote code execution (RCE) by swapping out the requested binary with an attacker controlled binary if the attacker is on the network or positioned in between the user and the remote server.

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 · high confidence

The headless-browser-lite npm package downloads PhantomJS and SlimerJS binary executables over unencrypted HTTP connections instead of HTTPS. This allows a network-based attacker positioned between the user and the download server to perform a man-in-the-middle (MITM) attack, intercepting the binary download and replacing it with a malicious executable, potentially leading to remote code execution on the victim's machine.

MitigationReplace all HTTP download URLs with HTTPS equivalents and implement cryptographic verification (e.g., SHA-256 checksums or GPG signatures) for downloaded binaries to ensure integrity before execution.

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
Headless Browser LiteApplication
Affected:< 2015.4.18-a

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/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. Check if headless-browser-lite is installed
    Run 'npm list headless-browser-lite' in the project directory or check package.json dependencies
    Affected if The package appears in installed dependencies or package.json
  2. Determine the installed version
    Run 'npm list headless-browser-lite' to see the version number, or check the version in node_modules/headless-browser-lite/package.json
    Affected if The version is less than 2015.4.18-a (e.g., 2015.4.17-a or earlier)
  3. Inspect package source for HTTP download URLs
    Examine the main JavaScript file in node_modules/headless-browser-lite/ and search for URLs starting with 'http://' (not 'https://') pointing to phantomjs or slimerjs download locations
    Affected if Any download URLs use http:// instead of https://
  4. Check .npmrc or package configuration for HTTP URLs
    Review any configuration files in the headless-browser-lite package directory for download URLs and verify they do not use HTTPS
    Affected if Configured download endpoints use unencrypted HTTP
  5. Verify binary download behavior
    Temporarily monitor network traffic or review package installation logs for outgoing HTTP connections to download servers (e.g., bitbucket.org, sourceforge.net)
    Affected if The package attempts to download binaries over unencrypted HTTP connections

The environment is affected if headless-browser-lite version < 2015.4.18-a is installed and the package code or configuration contains HTTP download URLs for PhantomJS or SlimerJS binaries.

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.

From vendor data
Upgrade available Upgrade to 2015.4.18-a or later
Fixed in 2015.4.18-a
Interim mitigation

Replace all HTTP download URLs with HTTPS equivalents and implement cryptographic verification (e.g., SHA-256 checksums or GPG signatures) for downloaded binaries to ensure integrity before execution.

Fix this in Headless Browser Lite Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2016-10625 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