Security readout for executives and security teams
Plain-English summary
The affected Node module downloads the Selenium Jar over unencrypted HTTP. Someone positioned on the network could replace that download with a malicious binary, creating possible remote code execution when the binary is used. The sources list all versions as affected, but do not provide a CVSS score or fixed version.
Executive priority
Prioritize removal or replacement if the module exists in build or test pipelines. The main business risk is supply-chain compromise through binary substitution, not broad internet-facing exploitation. No active exploitation evidence is provided.
Technical view
CVE-2016-10691 affects the windows-seleniumjar node module. It retrieves binary resources over HTTP, mapped to CWE-311. A network-positioned attacker could perform a MITM substitution of the requested Selenium Jar with attacker-controlled content. Impact is described as possible RCE, dependent on installation or execution context.
Likely exposure
Exposure is likely limited to projects, build systems, or developer machines that depend on the windows-seleniumjar node module. The source bundle states all versions are affected. Risk is higher where dependency installation occurs on untrusted networks or where downloaded binaries are executed automatically.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not marked KEV. Exploitation requires an attacker positioned between the user and the remote server during the HTTP binary download. The practical impact depends on whether the substituted Jar is executed in the victim environment.
Researcher notes
Evidence is narrow but clear: all versions are listed affected, with HTTP binary retrieval enabling MITM substitution and possible RCE. Missing details include CVSS, patched release, proof of exploitation, and current package status. Treat findings as dependency and build-chain exposure.
Mitigation direction
- Check vendor or package advisory guidance; no fixed version is specified in the provided sources.
- Remove or replace windows-seleniumjar where feasible.
- Avoid HTTP-fetched binary dependencies in build and developer workflows.
- Use trusted, authenticated sources for Selenium binaries.
- Restrict dependency installation to trusted networks and controlled CI environments.
Validation and detection
- Search dependency manifests and lockfiles for windows-seleniumjar.
- Review CI and build environments for use of this module.
- Confirm whether Selenium Jar downloads occur over HTTP.
- Check whether downloaded binaries are executed during install or tests.
- Document any remaining use and compensating network controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-311: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2016-10691 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://nodesecurity.io/advisories/296CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Encryption of Sensitive Data
Missing Encryption of Sensitive Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.