Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2025-5095 β€” AI Deep Analysis Summary

CVSS 9.8 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: A critical **Access Control Error** in Burk Technology ARC Solo. The password change mechanism fails to verify identity properly.…

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: **CWE-306** (Missing Authentication for Critical Function). The flaw lies in the **password reset/change logic**, which does not strictly validate the user's identity before allowing changes.

Q3Who is affected? (Versions/Components)

🏒 **Affected Vendor**: Burk Technology. πŸ“¦ **Product**: ARC Solo (IP-based remote monitoring & control system). ⚠️ **Version**: Specifically affects versions **older than 1.0.60**.

Q4What can hackers do? (Privileges/Data)

πŸ’€ **Attacker Capabilities**: Full **Device Takeover**. Due to CVSS 3.1 High severity (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), attackers gain **High Confidentiality, Integrity, and Availability** impact.…

Q5Is exploitation threshold high? (Auth/Config)

πŸ”“ **Exploitation Threshold**: **LOW**. The CVSS vector shows **AV:N** (Network), **AC:L** (Low Complexity), **PR:N** (No Privileges Required), and **UI:N** (No User Interaction).…

Q6Is there a public Exp? (PoC/Wild Exploitation)

πŸ”₯ **Public Exploit**: **YES**. A Python POC is available on GitHub (TeteuXD2). It involves editing `Login.htm` and `post.json` to target the victim's IP/Port. ⚠️ **Warning**: Works only on versions < 1.0.60.

Q7How to self-check? (Features/Scanning)

πŸ” **Self-Check**: 1. Identify if you run Burk ARC Solo. 2. Check version number (must be < 1.0.60). 3. Use the provided GitHub POC script to test if the password change endpoint is vulnerable to identity bypass.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Official Fix**: Update to **version 1.0.60 or higher**. The POC explicitly states it does not work on newer versions, implying the fix is in the updated firmware/software release.

Q9What if no patch? (Workaround)

🚧 **No Patch Workaround**: If you cannot update immediately: 1. **Isolate** the device from the public internet. 2. Restrict access via **Firewall rules** to trusted IPs only. 3.…

Q10Is it urgent? (Priority Suggestion)

⚑ **Urgency**: **CRITICAL**. With CVSS High severity and public POCs, this is an active threat. Prioritize patching to **v1.0.60+** immediately to prevent remote device takeover.