CVE-2022-36112: CWE-918: Server-Side Request Forgery (SSRF) in glpi-project glpi
GLPI stands for Gestionnaire Libre de Parc Informatique and is a Free Asset and IT Management Software package, that provides ITIL Service Desk features, licenses tracking and software auditing. Usage of RSS feeds or extenal calendar in planning is subject to SSRF exploit. Server-side requests can be used to scan server port or services opened on GLPI server or its private network. Queries responses are not exposed to end-user (blind SSRF). Users are advised to upgrade to version 10.0.3 to resolve this issue. There are no known workarounds.
AI Analysis
Technical Summary
CVE-2022-36112 is a Server-Side Request Forgery (SSRF) vulnerability identified in versions of the GLPI software prior to 10.0.3. GLPI (Gestionnaire Libre de Parc Informatique) is an open-source IT asset and service management software widely used for ITIL service desk operations, license tracking, and software auditing. The vulnerability arises from the handling of external resources such as RSS feeds or external calendars within the planning module. An attacker can exploit this SSRF flaw by manipulating server-side requests to make the GLPI server initiate HTTP requests to arbitrary internal or external resources. Although the responses to these requests are not directly exposed to the attacker (blind SSRF), the attacker can leverage this to scan internal network ports or services accessible from the GLPI server, potentially mapping internal infrastructure or identifying vulnerable services behind firewalls. This can lead to further exploitation or lateral movement within the network. The vulnerability does not require user interaction beyond having access to the affected GLPI instance, and no authentication requirements are explicitly stated, though exploitation feasibility depends on attacker access to the GLPI interface. The vendor has addressed the issue in version 10.0.3, and no known workarounds exist. There are no known exploits in the wild at this time, but the risk remains due to the nature of SSRF vulnerabilities and the critical role GLPI plays in IT management environments.
Potential Impact
For European organizations, the impact of this SSRF vulnerability can be significant, especially for entities relying on GLPI for IT asset management and service desk operations. Exploitation could allow attackers to perform internal reconnaissance, identifying open ports and services within the organization's private network that are otherwise inaccessible externally. This can facilitate subsequent attacks such as privilege escalation, data exfiltration, or deployment of malware. Given that GLPI often manages sensitive IT infrastructure information, unauthorized access or disruption could compromise confidentiality and integrity of IT asset data. Additionally, if attackers leverage SSRF to access internal services, availability of critical IT management functions could be disrupted. The blind nature of the SSRF limits direct data leakage but does not mitigate the risk of internal network mapping and follow-on attacks. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and government, could face regulatory and reputational consequences if this vulnerability is exploited.
Mitigation Recommendations
The primary mitigation is to upgrade GLPI installations to version 10.0.3 or later, where the SSRF vulnerability has been patched. Organizations should prioritize this update in their patch management cycles. Beyond upgrading, administrators should implement network segmentation to limit the GLPI server's ability to reach sensitive internal services unnecessarily. Employing strict egress filtering and firewall rules to restrict outbound requests from the GLPI server can reduce SSRF exploitation impact. Additionally, monitoring and logging outbound requests from the GLPI server can help detect anomalous activity indicative of SSRF attempts. If upgrading immediately is not feasible, disabling or restricting the use of external RSS feeds and calendar integrations in GLPI can reduce attack surface. Finally, applying the principle of least privilege to the GLPI service account and ensuring that the server runs with minimal network permissions can further mitigate risk.
Affected Countries
France, Germany, United Kingdom, Italy, Spain, Netherlands, Belgium, Sweden
CVE-2022-36112: CWE-918: Server-Side Request Forgery (SSRF) in glpi-project glpi
Description
GLPI stands for Gestionnaire Libre de Parc Informatique and is a Free Asset and IT Management Software package, that provides ITIL Service Desk features, licenses tracking and software auditing. Usage of RSS feeds or extenal calendar in planning is subject to SSRF exploit. Server-side requests can be used to scan server port or services opened on GLPI server or its private network. Queries responses are not exposed to end-user (blind SSRF). Users are advised to upgrade to version 10.0.3 to resolve this issue. There are no known workarounds.
AI-Powered Analysis
Technical Analysis
CVE-2022-36112 is a Server-Side Request Forgery (SSRF) vulnerability identified in versions of the GLPI software prior to 10.0.3. GLPI (Gestionnaire Libre de Parc Informatique) is an open-source IT asset and service management software widely used for ITIL service desk operations, license tracking, and software auditing. The vulnerability arises from the handling of external resources such as RSS feeds or external calendars within the planning module. An attacker can exploit this SSRF flaw by manipulating server-side requests to make the GLPI server initiate HTTP requests to arbitrary internal or external resources. Although the responses to these requests are not directly exposed to the attacker (blind SSRF), the attacker can leverage this to scan internal network ports or services accessible from the GLPI server, potentially mapping internal infrastructure or identifying vulnerable services behind firewalls. This can lead to further exploitation or lateral movement within the network. The vulnerability does not require user interaction beyond having access to the affected GLPI instance, and no authentication requirements are explicitly stated, though exploitation feasibility depends on attacker access to the GLPI interface. The vendor has addressed the issue in version 10.0.3, and no known workarounds exist. There are no known exploits in the wild at this time, but the risk remains due to the nature of SSRF vulnerabilities and the critical role GLPI plays in IT management environments.
Potential Impact
For European organizations, the impact of this SSRF vulnerability can be significant, especially for entities relying on GLPI for IT asset management and service desk operations. Exploitation could allow attackers to perform internal reconnaissance, identifying open ports and services within the organization's private network that are otherwise inaccessible externally. This can facilitate subsequent attacks such as privilege escalation, data exfiltration, or deployment of malware. Given that GLPI often manages sensitive IT infrastructure information, unauthorized access or disruption could compromise confidentiality and integrity of IT asset data. Additionally, if attackers leverage SSRF to access internal services, availability of critical IT management functions could be disrupted. The blind nature of the SSRF limits direct data leakage but does not mitigate the risk of internal network mapping and follow-on attacks. Organizations in sectors with stringent data protection requirements, such as finance, healthcare, and government, could face regulatory and reputational consequences if this vulnerability is exploited.
Mitigation Recommendations
The primary mitigation is to upgrade GLPI installations to version 10.0.3 or later, where the SSRF vulnerability has been patched. Organizations should prioritize this update in their patch management cycles. Beyond upgrading, administrators should implement network segmentation to limit the GLPI server's ability to reach sensitive internal services unnecessarily. Employing strict egress filtering and firewall rules to restrict outbound requests from the GLPI server can reduce SSRF exploitation impact. Additionally, monitoring and logging outbound requests from the GLPI server can help detect anomalous activity indicative of SSRF attempts. If upgrading immediately is not feasible, disabling or restricting the use of external RSS feeds and calendar integrations in GLPI can reduce attack surface. Finally, applying the principle of least privilege to the GLPI service account and ensuring that the server runs with minimal network permissions can further mitigate risk.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2022-07-15T00:00:00.000Z
- Cisa Enriched
- true
Threat ID: 682d9845c4522896dcbf3e75
Added to database: 5/21/2025, 9:09:25 AM
Last enriched: 6/22/2025, 9:50:07 PM
Last updated: 10/16/2025, 6:13:19 AM
Views: 24
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-0275: CWE-306 Missing Authentication for Critical Function in HCL Software BigFix Mobile
MediumCVE-2025-0274: CWE-306 Missing Authentication for Critical Function in HCL Software BigFix Modern Client Management
MediumCVE-2025-11814: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in Brainstorm Force Ultimate Addons for WPBakery
MediumCVE-2025-62580: CWE-121 Stack-based Buffer Overflow in Delta Electronics ASDA-Soft
HighCVE-2025-62579: CWE-121 Stack-based Buffer Overflow in Delta Electronics ASDA-Soft
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.