GitHub Advisoryadvisory · npm

GHSA-g2gw-q38m-vjfc Lokka: Azure Resource Manager URL path validation issue

HIGH Published 2026-06-19 Modified 2026-06-19 Official page ↗
Ecosystem
npm
Packages
@merill/lokka
Severity
High
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Weaknesses
CWE-918
Reviewed
2026-06-19

Affected packages

• npm @merill/lokka: < 2.1.2 → fixed in 2.1.2

Description

Lokka versions prior to 2.1.2 constructed Azure Resource Manager request URLs using direct string concatenation with user-controlled path input. Specially crafted path values could alter URL authority parsing and cause Azure Resource Manager bearer tokens to be sent to an unintended host. Version 2.1.2 fixes the issue by validating Azure paths before token acquisition and constructing Azure Resource Manager URLs with the standard URL API while preserving the expected management.azure.com host. Reported by 정해창

Related

Weakness · CWE (1)

  • CWE-918 Server-Side Request Forgery weakness

References