How severe is GHSA-724c-6vrf-99rq?

No CVSS score has been assigned to GHSA-724c-6vrf-99rq yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-724c-6vrf-99rq?

GHSA-724c-6vrf-99rq affects the following packages: loopback (npm), loopback (npm). Ecosystems affected: npm.

How do I fix GHSA-724c-6vrf-99rq?

Update loopback to 2.42.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-724c-6vrf-99rq is resolved across your whole dependency graph.

How do I detect GHSA-724c-6vrf-99rq in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loopback, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-724c-6vrf-99rq if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-724c-6vrf-99rq actively exploited in the wild?

No public exploit code has been indexed for GHSA-724c-6vrf-99rq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-724c-6vrf-99rq published, and has it been updated?

GHSA-724c-6vrf-99rq was published on September 2, 2020 and was last updated on September 27, 2021. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Sensitive Data Exposure in loopbackGHSA-724c-6vrf-99rq

GHSA-724c-6vrf-99rq is a security vulnerability in loopback. A fix is available for loopback — see the affected versions and patch details below.

Published

Sep 2, 2020

Updated

Sep 27, 2021

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 27, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

256other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

loopbacknpm

51Kdownloads / week

Description

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`loopback`	all versions	2.42.0`npm install loopback@2.42.0`
📦npm	`loopback`	≥ 3.0.0&&< 3.26.0	3.26.0`npm install loopback@3.26.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loopback, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update loopback to 2.42.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-724c-6vrf-99rq is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-724c-6vrf-99rq in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works