Security readout for executives and security teams
Plain-English summary
This affects an old Node.js module used to install and launch Selenium Server. Versions before 3.0.1 downloaded binary resources over unencrypted HTTP. A network-positioned attacker could potentially replace that download, creating possible remote code execution during installation or launch workflows.
Executive priority
Treat this as a targeted supply-chain cleanup rather than an emergency internet-facing incident. Prioritize systems that build, test, or install dependencies on shared or untrusted networks.
Technical view
baryton-saxophone versions below 3.0.1 used HTTP for binary resource downloads. The weakness is classified as CWE-311 and creates a man-in-the-middle dependency-download risk. The cited CVE text says attacker-controlled binary substitution may lead to RCE if the attacker is on-path between the user and remote server.
Likely exposure
Exposure is limited to environments using the baryton-saxophone Node module below 3.0.1, especially developer, CI, or test systems that install or run Selenium Server through this package.
Exploitation context
The source bundle does not cite active exploitation, and the CVE is not listed as KEV. Exploitation requires a network or routing position capable of tampering with the HTTP binary download.
Researcher notes
Evidence is concise and lacks CVSS details, exploit telemetry, or deeper advisory text in the bundle. The main validation target is dependency presence and version, then whether install or launch workflows could fetch binaries over HTTP.
Mitigation direction
- Upgrade baryton-saxophone to version 3.0.1 or later.
- Remove the dependency if it is no longer needed.
- Review vendor or package advisory guidance before deployment.
- Avoid affected installs on untrusted or interceptable networks.
Validation and detection
- Check package manifests and lockfiles for baryton-saxophone versions below 3.0.1.
- Review CI and developer build dependencies for transitive use of the module.
- Confirm Selenium Server installation paths no longer rely on HTTP binary downloads.
- Document remediation evidence for any affected repository.
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-10573 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/240CVE 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.