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

Goal: 1000 CNY ยท Raised: 1359 CNY

100%

CVE-2018-12634 โ€” AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

๐Ÿšจ **Essence**: A critical info leak in Circontrol CirCarLife Scada. ๐Ÿ“‰ **Consequences**: Attackers can grab sensitive internal data just by sending a direct HTTP request to specific URIs. No complex attack needed!

Q2Root Cause? (CWE/Flaw)

๐Ÿ›ก๏ธ **Root Cause**: Improper Access Control / Sensitive Information Exposure. ๐Ÿ› **Flaw**: The system fails to restrict access to diagnostic endpoints like `html/log` and `services/system/info.html`.โ€ฆ

Q3Who is affected? (Versions/Components)

๐Ÿข **Vendor**: Circontrol (Spain). ๐Ÿš— **Product**: CirCarLife Scada (Parking/EV Charging automation). ๐Ÿ“ฆ **Affected Version**: Specifically **v4.2.4**. (Likely earlier versions too, but 4.2.4 is confirmed).

Q4What can hackers do? (Privileges/Data)

๐Ÿ’ป **Hackers' Power**: Remote attackers. ๐Ÿ”“ **Data Access**: Can retrieve sensitive system info and logs. ๐Ÿ•ต๏ธ **Impact**: Reconnaissance goldmine! They get a clear picture of your system architecture and internal states.

Q5Is exploitation threshold high? (Auth/Config)

โšก **Threshold**: VERY LOW. ๐Ÿšช **Auth**: None required! ๐ŸŒ **Config**: Just a direct URL request. If the URI is accessible, you're in. It's an open door for anyone on the network/internet.

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

๐Ÿ”ฅ **Public Exp?**: YES! ๐Ÿ“œ **PoC**: Available via Nuclei templates (ProjectDiscovery). ๐Ÿ’ฃ **Wild Exp**: Exploit-DB ID **45384** exists. It's easy to automate and scan for.

Q7How to self-check? (Features/Scanning)

๐Ÿ” **Self-Check**: Scan for these exact paths: `/html/log` and `/services/system/info.html`. ๐Ÿ› ๏ธ **Tool**: Use Nuclei or simple curl requests. If you get a response with system info/logs, you're vulnerable!

Q8Is it fixed officially? (Patch/Mitigation)

๐Ÿฉน **Official Fix**: The description notes the issue exists **before v4.3**. โœ… **Status**: Upgrading to **v4.3 or later** is the official mitigation path mentioned in the PoC readme.

Q9What if no patch? (Workaround)

๐Ÿšง **No Patch?**: Block external access to these URIs via WAF or Firewall rules. ๐Ÿšซ **Action**: Deny requests to `/html/log` and `/services/system/info.html` from untrusted networks immediately.

Q10Is it urgent? (Priority Suggestion)

๐Ÿšจ **Urgency**: HIGH. โš ๏ธ **Priority**: Patch ASAP! Since it requires no auth and public exploits exist, automated bots are likely scanning for this. Don't wait!