Skip to main content

CVE-2022-35945: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in glpi-project glpi

Medium
Published: Wed Sep 14 2022 (09/14/2022, 17:45:12 UTC)
Source: CVE
Vendor/Project: glpi-project
Product: 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. Information associated to registration key are not properly escaped in registration key configuration page. They can be used to steal a GLPI administrator cookie. Users are advised to upgrade to 10.0.3. There are no known workarounds for this issue. ### Workarounds Do not use a registration key created by an untrusted person.

AI-Powered Analysis

AILast updated: 06/22/2025, 22:49:41 UTC

Technical Analysis

CVE-2022-35945 is a cross-site scripting (XSS) vulnerability identified in the GLPI (Gestionnaire Libre de Parc Informatique) software, versions 9.5.0 up to but not including 10.0.3. GLPI is an open-source IT asset and service management tool widely used for ITIL service desk functions, license tracking, and software auditing. The vulnerability arises from improper neutralization of input during web page generation, specifically on the registration key configuration page. The issue is that information associated with the registration key is not properly escaped, allowing an attacker to inject malicious scripts. This can lead to the theft of administrator cookies if an administrator views a crafted registration key entry. The vulnerability falls under CWE-79, which concerns improper input sanitization leading to XSS attacks. Exploitation does not require prior authentication but does require that the attacker can supply or influence the registration key data viewed by an administrator. There are no known workarounds other than avoiding the use of registration keys from untrusted sources. The vendor has addressed this vulnerability in GLPI version 10.0.3, and users are strongly advised to upgrade to this or later versions to mitigate the risk. No known exploits have been reported in the wild as of the publication date, but the potential for cookie theft and subsequent session hijacking poses a significant risk to confidentiality and integrity of administrative sessions.

Potential Impact

For European organizations using GLPI versions prior to 10.0.3, this vulnerability could lead to unauthorized access to administrative sessions through cookie theft, enabling attackers to perform administrative actions, manipulate IT asset data, or disrupt service desk operations. The compromise of administrative accounts could result in data breaches, unauthorized changes to IT infrastructure management, and potential disruption of IT service management processes. Given GLPI's role in managing licenses, software auditing, and service desk tickets, exploitation could impact operational integrity and availability of IT services. The risk is heightened in environments where GLPI is exposed to untrusted users who can submit registration keys, such as in multi-tenant or externally accessible deployments. Although no active exploitation is known, the medium severity rating reflects the moderate ease of exploitation combined with the significant impact on confidentiality and integrity if successful.

Mitigation Recommendations

1. Immediate upgrade to GLPI version 10.0.3 or later to apply the official patch addressing the XSS vulnerability. 2. Restrict access to the registration key configuration page to trusted administrators only, ideally limiting network exposure through firewalls or VPNs. 3. Implement strict input validation and sanitization controls on any user-supplied data related to registration keys, if customization is possible. 4. Monitor administrative sessions for unusual activity that could indicate session hijacking attempts. 5. Educate administrators to avoid using registration keys from untrusted sources and to be cautious when reviewing registration key data. 6. Employ Content Security Policy (CSP) headers to reduce the impact of potential XSS attacks by restricting script execution. 7. Regularly audit GLPI logs and configurations for signs of tampering or exploitation attempts. 8. Consider deploying web application firewalls (WAFs) with rules tuned to detect and block XSS payloads targeting GLPI.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2022-07-15T00:00:00.000Z
Cisa Enriched
true

Threat ID: 682d9844c4522896dcbf3d1e

Added to database: 5/21/2025, 9:09:24 AM

Last enriched: 6/22/2025, 10:49:41 PM

Last updated: 8/4/2025, 12:55:01 AM

Views: 13

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats