Lokka: Azure Resource Manager URL path validation issue
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
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 정해창 <[email protected]>
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | @merill/lokka (npm) | before 2.1.2 | 2.1.2 | Patch available | GHSA-g2gw-q38m-vjfc |
- @merill/lokka (npm) Vendor— Affected before 2.1.2 Fixed in 2.1.2 Patch available GHSA-g2gw-q38m-vjfc
Remediation
- Fix · GHSA-g2gw-q38m-vjfc @merill/lokka (npm) Fixed in 2.1.2 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-g2gw-q38m-vjfc
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences