Improper Authorization in loopback

loopback Updated 02 Oct 2025

Summary

02/09/2020
HIGH
Yes i
High
Not published

GHSA-8wgc-jjvv-cv6v: Improper Authorization in loopback. Affects loopback across 2 version ranges.

< 2.40.0 >= 3.0.0, < 3.22.0

Fixed in 2.40.0 or 3.22.0, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Loopback is an open-source Node.js framework for building APIs and microservices. It provides a set of tools and conventions to quickly create robust and scalable applications. Loopback includes an AccessToken model that is used for authentication and authorization. However, vulnerable versions of loopback suffer from an Improper Authorization vulnerability, which allows attackers to create Authentication Tokens on behalf of other users. This can lead to unauthorized access to user data and privileges.

Vulnerability Detail

The vulnerability in loopback arises from the AccessToken model being publicly exposed. Attackers can exploit this by creating Authorization Tokens for any user if they know the target's userId. By doing so, they can gain access to the user's data and privileges, potentially leading to unauthorized actions and data breaches.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.40.0 2.40.0
    npm install loopback@2.40.0
  • >= 3.0.0, < 3.22.0 3.22.0
    npm install loopback@3.22.0

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. It is advised to follow the recommended fix and upgrade to the patched versions of loopback.

Conclusion

The Improper Authorization vulnerability in loopback can lead to unauthorized access to user data and privileges. It is crucial to upgrade to the recommended versions to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for loopback →

Share this vulnerability

FAQ

Loopback is an open-source Node.js framework for building APIs and microservices. It provides a set of tools and conventions to quickly create robust and scalable applications.

The AccessToken model in loopback is used for authentication and authorization. It represents an access token that grants permissions to perform certain actions or access specific resources.

The Improper Authorization vulnerability in loopback occurs when the AccessToken model is publicly exposed. This allows attackers to create Authentication Tokens for any user by knowing their userId, leading to unauthorized access to user data and privileges.

The potential consequences of this vulnerability include unauthorized access to user data, privilege escalation, and potential data breaches. Attackers can exploit this vulnerability to perform actions on behalf of other users without their consent.

To fix this vulnerability, you should upgrade your loopback application to the recommended versions: 2.40.0 or later for loopback 2.x, and 3.22.0 or later for loopback 3.x. This will ensure that the Improper Authorization vulnerability is patched.

Related vulnerabilities

Recent vulnerabilities recorded for loopback.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.40.0 2.40.0
    npm install loopback@2.40.0
  • >= 3.0.0, < 3.22.0 3.22.0
    npm install loopback@3.22.0

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback