Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
The init guard middleware in Qinglong only checks /api/user/init paths but not /open/user/init, which is whitelisted from JWT authentication and rewritten to /api/user/init after the guard has already passed, allowing unauthenticated admin credential reset on initialized instances. Affected Package - Ecosystem: npm - Package: whyour/qinglong - Affected versions: < 6bec52dca158 - Patched versions: = 6bec52dca158 Severity Medium CWE CWE-287 — Improper Authentication Details The Qinglong panel has an initialization endpoint (/api/user/init) that allows setting admin credentials. Once the system is initialized, an init guard middleware is supposed to block further calls. The middleware in back/loaders/express.ts only checks: However, the application also has a URL rewrite rule: rewrite('/open/', '/api/$1'). The /open/ paths are whitelisted from JWT authentication. The middleware ordering creates the bypass: first, JWT auth sees /open/ paths match the whitelist regex and skips…
Recommended action: Upgrade to 2.20.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A security vulnerability has been detected in whyour qinglong up to 2.20.1. Affected is an unknown function of the file back/loaders/express.ts of the component API Interface. The manipulation of the argument command leads to protection mechanism failure. The attack may be initiated remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 2.20.2 is able to address this issue. The identifier of the patch is 6bec52dca158481258315ba0fc2f11206df7b719. It is advisable to upgrade the affected component. The code maintainer was informed beforehand about the issues. He reacted very fast and highly professional.
Recommended action: Upgrade to 2.20.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.