Sensitive Data Exposure in loopback

published 2020-09-02 6y ago modified 2021-09-27 5y ago

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

Versions of `loopback` prior to 3.26.0 (3.x) and 2.42.0 (2.x) are vulnerable to Sensitive Data Exposure. Invalid API requests to the login endpoint may return information about the first user in the database. This can be used alongside other attacks for credential theft.

## Recommendation

If you're using `loopback` 3.x upgrade to version 3.26.0 or later. If you're using `loopback` 2.x upgrade to version 2.42.0 or later.

Patch / fix

fixed in 1

npm loopback 2.42.0, 3.26.0

Is GHSA-724c-6vrf-99rq 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

Affected packages

ecosystem	package	affected	fixed in
npm	loopback	<2.42.0 >=3.0.0, <3.26.0	2.42.0 3.26.0

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

GitHub Advisory GHSA-724c-6vrf-99rq

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.