CVE-2016-10633
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 · unediteddwebp-bin is a dwebp node.js wrapper that convert WebP into PNG. dwebp-bin 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 confidencedwebp-bin is a Node.js wrapper for the dwebp binary that converts WebP images to PNG. The package downloads its binary resources over HTTP instead of HTTPS, allowing a man-in-the-middle attacker to intercept the connection and substitute a malicious binary. If successfully exploited, this could result in remote code execution on systems where this package is installed.
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<= 0.1.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if dwebp-bin is installedSearch for dwebp-bin in your package.json dependencies or run 'npm list dwebp-bin' or 'yarn list dwebp-bin' in your project directoryAffected if dwebp-bin appears in your installed dependencies
-
Check the installed version numberRun 'npm list dwebp-bin --depth=0' or 'yarn list dwebp-bin --depth=0' to see the exact version installed, or check package.jsonAffected if The version is 0.1.6 or lower (any version <= 0.1.6)
-
Inspect the package download sourceExamine the package's source code in node_modules/dwebp-bin/ and look for the download URL configuration (often in a file like download.js, index.js, or a configuration object)Affected if The download URL uses HTTP instead of HTTPS (starts with http://)
-
Verify the binary file originCheck if the dwebp binary in node_modules/dwebp-bin/vendor/ or similar path was downloaded from a non-HTTPS source by inspecting the package's install script or download mechanismAffected if The binary was retrieved over an unencrypted HTTP connection
You are affected if dwebp-bin version 0.1.6 or lower is installed and uses HTTP for downloading binary resources, as this allows potential remote code execution via a man-in-the-middle attack during package installation.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace dwebp-bin with a secure alternative that uses HTTPS for binary downloads, or audit and verify the integrity of any existing dwebp binary installations. Consider using @ffmpeg-installer/ffmpeg or similar packages that employ secure download mechanisms.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10633 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-10633 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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