Insecure Defaults Leads to Potential MITM in ezseed-transmission

published 2020-09-01 6y ago modified 2023-11-08 3y ago also GHSA-p788-rj37-357w

cvss: 4.2; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no EPSS score yet
public exploits: 0; none known

Affected versions of `ezseed-transmission` download and run a script over an HTTP connection.

An attacker in a privileged network position could launch a Man-in-the-Middle attack and intercept the script, replacing it with malicious code, completely compromising the system running `ezseed-transmission`.

## Recommendation

Update to version 0.0.15 or later.

Patch / fix

fixed in 1

npm ezseed-transmission 0.0.15

Is CVE-2016-1000224 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	4.2	CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	ezseed-transmission	>=0.0.10, <0.0.15	0.0.15

Classification

Weakness

CWE-295 Improper Certificate Validation
CWE-300 Channel Accessible by Non-Endpoint

References

nvd.nist.gov /vuln/detail/CVE-2016-1000224
advisory
snyk.io /vuln/npm:ezseed-transmission:20160729
web
npmjs.com /advisories/114
web

Sources

GitHub Advisory GHSA-p788-rj37-357w

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.