This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis β
Q1What is this vulnerability? (Essence + Consequences)
π¨ **Essence**: Glances < 4.5.2 leaks embedded HTTP basic credentials via `/api/4/serverslist` in Central Browser mode.β¦
π‘οΈ **CWE**: CWE-200 (Information Exposure). π **Flaw**: The API endpoint fails to sanitize server objects, exposing sensitive authentication data that should remain hidden from unauthenticated users.
Q3Who is affected? (Versions/Components)
π¦ **Vendor**: Nicolargo. π¦ **Product**: Glances. β οΈ **Affected**: Versions **prior to 4.5.2**. β **Fixed**: Version 4.5.2 and later.
Q4What can hackers do? (Privileges/Data)
π΅οΈ **Action**: Retrieve embedded HTTP Basic Auth credentials. π **Impact**: High Confidentiality & Integrity impact. Hackers gain access to downstream servers using stolen credentials without needing direct access.
Q5Is exploitation threshold high? (Auth/Config)
π **Auth**: None required (PR:N). π **Access**: Network accessible (AV:N). π **Threshold**: **LOW**. Any network user can trigger the leak via the API endpoint without logging in.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π« **Public Exp**: No PoC provided in data. π **Risk**: While no wild exploit exists yet, the low barrier to entry makes it highly susceptible to rapid automation by threat actors.
Q7How to self-check? (Features/Scanning)
π **Check**: Scan for Glances Central Browser mode. π‘ **Test**: Request `GET /api/4/serverslist` without auth. π **Verify**: Inspect JSON response for embedded `username`/`password` fields in server objects.
Q8Is it fixed officially? (Patch/Mitigation)
β **Patch**: Yes! Upgrade to **Glances 4.5.2**.β¦
π **Workaround**: Disable Central Browser mode if not needed. π« **Network**: Restrict access to the Glances API port via firewall rules. π§Ή **Audit**: Regularly rotate credentials for downstream servers.
Q10Is it urgent? (Priority Suggestion)
π₯ **Priority**: **HIGH**. CVSS Score indicates High Confidentiality/Integrity impact with no auth required. Immediate patching or mitigation is strongly recommended to prevent credential theft.