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**: Code Injection in `displayServiceStatus.php`. π₯ **Consequences**: Attackers can inject malicious commands via the `command_line` parameter. This breaks the security boundary of the IT monitoring software.
Q2Root Cause? (CWE/Flaw)
π‘οΈ **Root Cause**: Insufficient input validation/filtering. π **Flaw**: The script fails to sanitize the `command_line` input, allowing raw code execution.β¦
π¦ **Affected**: Centreon 2.5.1 and Centreon Enterprise Server (CES) 2.2. π₯οΈ **Component**: Specifically the `displayServiceStatus.php` script used for web-based Nagios management.
Q4What can hackers do? (Privileges/Data)
π» **Hacker Action**: Remote Command Injection. π **Privileges**: Likely allows execution of system commands with the web server's privileges.β¦
β‘ **Threshold**: Likely Low/Medium. π **Auth**: The reference mentions "unauthenticated remote command injection". This implies no login is needed to exploit the `command_line` flaw in the specific script.
Q6Is there a public Exp? (PoC/Wild Exploitation)
π’ **Public Exp?**: Yes. π **Evidence**: Full Disclosure mailing list post (Oct 2014) confirms multiple injections. GitHub commit and release notes confirm the vulnerability exists and was addressed.
Q7How to self-check? (Features/Scanning)
π **Self-Check**: Scan for Centreon versions 2.5.1 or CES 2.2. π― **Target**: Check if `displayServiceStatus.php` is accessible.β¦
β **Fixed**: Yes. π **Patch**: Centreon released version 2.5.3 and updated CES. π **Ref**: See Centreon 2.5.3 release notes and GitHub commit `cc21098` for the fix details.
Q9What if no patch? (Workaround)
π§ **Workaround**: If patching is delayed, restrict access to `displayServiceStatus.php` via firewall/WAF.β¦
π₯ **Urgency**: HIGH. π¨ **Reason**: Unauthenticated Remote Code Execution (RCE) is critical. β³ **Status**: Vulnerability is old (2014), but any unpatched legacy systems remain at immediate risk of total compromise.