dbcve.org
Prebuild LwipApplication · Prebuild Lwip Project

CVE-2016-10652

HIGH · 8.1 CVSS v3.0 Published 2018-06-04
Fix available
A fix is available. Upgrade to after 0.0.4 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
prebuild-lwip is a module for comprehensive, fast, and simple image processing and manipulation. prebuild-lwip downloads resources over HTTP, which leaves it vulnerable to MITM attacks.

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 prebuild-lwip npm package downloads prebuilt binaries and resources over unencrypted HTTP connections instead of HTTPS, allowing man-in-the-middle attackers to intercept and replace the downloaded content with malicious code during the installation process.

MitigationReplace all HTTP download URLs with HTTPS and implement integrity verification (e.g., checksums or Subresource Integrity) to ensure downloaded resources have not been tampered with.

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
Prebuild LwipApplication
Affected:<= 0.0.4

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 prebuild-lwip is installed
    Run 'npm list prebuild-lwip' or inspect your package.json dependencies
    Affected if prebuild-lwip with version 0.0.4 or lower appears in installed packages
  2. Identify the installed version
    Run 'npm list prebuild-lwip --depth=0' to see the exact version number
    Affected if The installed version is 0.0.4 or any lower version number
  3. Inspect the package download configuration
    Examine the package.json file in node_modules/prebuild-lwip/ and look for 'scripts' or 'binary' fields that specify download URLs
    Affected if HTTP (not HTTPS) URLs are found in download, tarball, or binary configuration fields
  4. Check install scripts for HTTP usage
    Review any preinstall/postinstall scripts in node_modules/prebuild-lwip/ for network requests using http:// URLs
    Affected if The package performs downloads over unencrypted HTTP during installation

You are affected if prebuild-lwip version 0.0.4 or lower is installed and the package downloads resources over HTTP instead of HTTPS.

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 a release after 0.0.4
Interim mitigation

Replace all HTTP download URLs with HTTPS and implement integrity verification (e.g., checksums or Subresource Integrity) to ensure downloaded resources have not been tampered with.

Fix this in Prebuild Lwip Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10652 — 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-2016-10652 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