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

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

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!