Summary
Combodo iTop contains a PHP object injection vulnerability in its user preference functionality that may allow attacker-controlled objects to be deserialized and used for code execution. The risk arises when untrusted or insufficiently protected preference data reaches the vulnerable processing path.
Affected context
The vulnerability occurs in iTop deployments where user preference data is accepted, stored, or processed through a PHP serialization or deserialization workflow without adequate trust-boundary controls. It is most relevant when an attacker can influence preference values or submit crafted data that is later interpreted by the application.
Exploit preconditions
- Attack surface: Web-accessible user preference functionality - Required access: An account or other application-level ability to reach and
influence the relevant preference data, depending on deployment controls
- Trigger point: Processing or deserialization of attacker-influenced user
preference data
- Why exploitation is possible: Serialized object data may be reconstructed
without sufficiently restricting permitted classes or validating its
origin, potentially enabling dangerous object behavior and code execution
Why this happens
The underlying issue is unsafe handling of serialized PHP objects in a user-controlled data path. When an application deserializes data without strict trust-boundary enforcement, class restrictions, and integrity checks, attackers may influence object construction and invoke dangerous behavior through available methods or gadget chains. This primarily maps to CWE-502, Deserialization of Untrusted Data, and may also involve CWE-94 when the resulting object behavior enables code execution.
Potential impact
- An attacker may execute arbitrary code with the privileges of the iTop process.
- The application could be compromised or used to access sensitive service-management data.
- Credentials, tokens, or configuration data could be exposed.
- The host or connected systems could be affected through lateral movement.
General mitigation guidance
Mitigation generally focuses on removing unsafe deserialization from user-controlled workflows and reducing trust in preference data. Secure patterns include using structured formats with strict schemas instead of native PHP object serialization, allowing only explicitly approved primitive data types, validating and normalizing values before storage and use, and applying integrity protection where state must be retained. Preference processing can also be isolated behind authorization checks, while the application should run with least privilege and minimal access to operating system resources. Vendor-provided security fixes should be incorporated through the organization's normal maintenance process.
How teams detect issues like this
Detection approaches include static analysis for PHP deserialization calls, dynamic object reconstruction, magic-method invocation, and preference handlers that accept serialized input. Code review should flag native object serialization across authentication or storage boundaries, missing class allowlists, and preference values used without integrity validation. Web application monitoring can identify unusual preference updates, unexpected serialized-object markers, and anomalous child-process activity. Automated security review tools may help enforce policies that prohibit unsafe deserialization in user-controlled paths.

