Severity: HIGH · Priority: P2 — exploitation attempt against a serious flaw, escalate on hit
This rule raises an alert when an attacker attempts to exploit a serious flaw in GLPI, a widely used open-source IT asset-management tool. GLPI's inventory feature accepts data from agents without requiring a login, and in vulnerable versions it fails to properly clean one of the values it receives — letting an unauthenticated attacker inject database commands. This can be used to read sensitive data from the database, including stored access tokens for user accounts, and can be chained with a second flaw to achieve full remote code execution on the server. Because GLPI is frequently connected to corporate directory services, a compromise can become a foothold into the wider network. This rule watches for the specific injection pattern used against the vulnerable inventory request.
A hit indicates an attempt to exploit this flaw against one of your servers. The flaw is unauthenticated and network-reachable, affects GLPI versions 10.0.0 through 10.0.17, and is fixed in 10.0.18. Treat an alert as an active exploitation attempt: confirm whether the targeted host runs GLPI and whether it is patched to 10.0.18 or later; if it is unpatched and the inventory feature is enabled, assume the attempt may have succeeded and escalate to incident response. Because a successful attack can steal account tokens, treat GLPI user credentials and API tokens as potentially exposed — rotate them — and check for follow-on activity such as unexpected authenticated sessions or signs of code execution. Updating to the fixed version, and disabling the inventory feature if it is not needed, are the definitive fixes.