Insecure Default Configuration in redbird

published 2019-06-06 7y ago modified 2021-08-04 5y ago

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

Versions of `redbird` prior to 0.9.1 have a vulnerable default configuration of allowing TLS 1.0 connections on `lib/proxy.js`. The package does not provide an option to disable TLS 1.0 which is deprecated and vulnerable.

## Recommendation

Upgrade to version 0.9.1 or later.

Patch / fix

links 2

github.com/OptimalBits/redbird@39c7a2d commit
github.com/OptimalBits/redbird#207 pull request

Is GHSA-8948-ffc6-jg52 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:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	redbird	<=0.9.0	no fix listed

Classification

Weakness

CWE-20 Improper Input Validation

References

Sources

GitHub Advisory GHSA-8948-ffc6-jg52

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.