CVE-2016-10693
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 · uneditedpm2-kafka is a PM2 module that installs and runs a kafka server pm2-kafka 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 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 pm2-kafka PM2 module downloads Kafka binary resources over plain HTTP instead of HTTPS, making the download process vulnerable to Man-in-the-Middle (MITM) attacks. An attacker positioned on the network could intercept and replace the binary resources with malicious code, potentially achieving 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= 1.0.0CVSS 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 pm2-kafka is installedInspect your project dependencies: examine package.json for 'pm2-kafka' in the dependencies or devDependencies section, or check if node_modules/pm2-kafka exists in your project directoryAffected if pm2-kafka is present in your project's dependencies or node_modules
-
Verify the installed versionRun 'npm list pm2-kafka' or check the version field in node_modules/pm2-kafka/package.json to determine the exact version installedAffected if The installed version is 1.0.0
-
Inspect package download scriptsExamine the scripts section in node_modules/pm2-kafka/package.json, particularly any postinstall or preinstall script that handles binary downloadsAffected if The package contains scripts that download external resources
-
Check for HTTP URLs in download configurationSearch the package directory for HTTP URLs (not HTTPS) in configuration files, install scripts, or any code that fetches Kafka binaries - use grep to search for 'http://' strings within the pm2-kafka package filesAffected if The package uses plain HTTP (http://) instead of HTTPS (https://) URLs for downloading resources
You are affected if pm2-kafka version 1.0.0 is installed and its install scripts or configuration use plain HTTP URLs to download Kafka binary resources, exposing the download process to Man-in-the-Middle attacks.
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 dataDo not use pm2-kafka in its current form; wait for a patched version that uses HTTPS for all resource downloads, or implement manual verification of binary checksums if immediate use is required.
- 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-10693 — 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-10693 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