CVE-2016-10668
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 · uneditedlibsbml is a module that installs Linux binaries for libSBML libsbml downloads 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 resources with an attacker controlled copy 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 confidenceThe libsbml npm package downloads Linux binary resources over HTTP instead of HTTPS, allowing man-in-the-middle attackers to intercept and substitute malicious code during the download process. This supply chain vulnerability could enable remote code execution if an attacker positioned on the network modifies the requested resources.
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.0.2CVSS 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.
-
Check if libsbml npm package is installedRun 'npm list libsbml' or check your package.json dependencies for the libsbml entryAffected if The package is listed in node_modules or package.json dependencies and the version is 0.0.2 or lower
-
Identify the installed version numberRun 'npm list libsbml --depth=0' or look for 'libsbml' in your package-lock.json to see the exact version installedAffected if The version is 0.0.2 or any version <= 0.0.2
-
Examine package source for HTTP download URLsLocate the package in node_modules/libsbml and search the source files (especially index.js, installer scripts, or any file containing download logic) for 'http://' URLs pointing to binary resourcesAffected if The package source contains HTTP (not HTTPS) URLs used to fetch binaries or resources during installation or runtime
-
Monitor network behavior during package loadIf possible, use a network proxy or monitoring tool to observe outbound connections when your application first requires or imports libsbmlAffected if The package makes HTTP (not HTTPS) requests to external servers to download binary or native components
You are affected if the libsbml npm package version 0.0.2 or lower is installed and the package fetches binary resources over unencrypted HTTP connections.
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 or fork the package to use HTTPS for all resource downloads, ideally with integrity verification (checksums or signatures) to ensure downloaded binaries have not been tampered with. Alternatively, consider using a secure alternative that doesn't fetch binaries over insecure channels.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10668 — 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-10668 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