Page 11 of 138 results (0.003 seconds)

CVSS: 6.0EPSS: 0%CPEs: 1EXPL: 0

12 May 2020 — In GLPI after 0.68.1 and before 9.4.6, multiple reflexive XSS occur in Dropdown endpoints due to an invalid Content-Type. This has been fixed in version 9.4.6. En GLPI versiones posteriores a 0.68.1 y anteriores a 9.4.6, se producen múltiples ataques de tipo XSS reflexivos en los endpoints Dropdown debido a un Content-Type no válido. Esto ha sido corregido en la versión 9.4.6. • https://github.com/glpi-project/glpi/commit/5e1c52c5e8a30ceb4e9572964da7ed89ddfb1aaf • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •

CVSS: 7.2EPSS: 2%CPEs: 1EXPL: 2

12 May 2020 — GLPI before before version 9.4.6 has a vulnerability involving a default encryption key. GLPIKEY is public and is used on every instance. This means anyone can decrypt sensitive data stored using this key. It is possible to change the key before installing GLPI. But on existing instances, data must be reencrypted with the new key. • https://github.com/indevi0us/CVE-2020-5248 • CWE-798: Use of Hard-coded Credentials •

CVSS: 7.6EPSS: 0%CPEs: 1EXPL: 1

05 May 2020 — In GLPI before version 9.4.6 there are multiple related stored XSS vulnerabilities. The package is vulnerable to Stored XSS in the comments of items in the Knowledge base. Adding a comment with content "<script>alert(1)</script>" reproduces the attack. This can be exploited by a user with administrator privileges in the User-Agent field. It can also be exploited by an outside party through the following steps: 1. • https://github.com/glpi-project/glpi/security/advisories/GHSA-3g3h-rwhr-7385 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •

CVSS: 9.3EPSS: 0%CPEs: 3EXPL: 0

05 May 2020 — In GLPI after version 0.83.3 and before version 9.4.6, the CSRF tokens are generated using an insecure algorithm. The implementation uses rand and uniqid and MD5 which does not provide secure values. This is fixed in version 9.4.6. En GLPI posterior a la versión 0.83.3 y versiones anteriores a 9.4.6, los tokens CSRF son generados usando un algoritmo no seguro. La implementación utiliza rand y uniqid y MD5 que no proporcionan valores seguros. • https://github.com/glpi-project/glpi/security/advisories/GHSA-w7q8-58qp-vmpf • CWE-327: Use of a Broken or Risky Cryptographic Algorithm •

CVSS: 6.1EPSS: 28%CPEs: 1EXPL: 0

05 May 2020 — In GLPI before version 9.4.6, there is a vulnerability that allows bypassing the open redirect protection based which is based on a regexp. This is fixed in version 9.4.6. En GLPI versiones anteriores a 9.4.6, se presenta una vulnerabilidad que permite omitir la protección de redireccionamiento abierto el cual es basada en un regexp. Esto es corregido en la versión 9.4.6. • https://github.com/glpi-project/glpi/security/advisories/GHSA-gxv6-xq9q-37hg • CWE-185: Incorrect Regular Expression CWE-601: URL Redirection to Untrusted Site ('Open Redirect') •

CVSS: 7.2EPSS: 0%CPEs: 3EXPL: 0

05 May 2020 — In GLPI from version 9.1 and before version 9.4.6, any API user with READ right on User itemtype will have access to full list of users when querying apirest.php/User. The response contains: - All api_tokens which can be used to do privileges escalations or read/update/delete data normally non accessible to the current user. - All personal_tokens can display another users planning. Exploiting this vulnerability requires the api to be enabled, a technician account. It can be mitigated by adding an applicatio... • https://github.com/glpi-project/glpi/security/advisories/GHSA-rf54-3r4w-4h55 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 7.6EPSS: 0%CPEs: 1EXPL: 0

05 May 2020 — In GLPI before version 9.4.6, there is a SQL injection vulnerability for all helpdesk instances. Exploiting this vulnerability requires a technician account. This is fixed in version 9.4.6. En GLPI versiones anteriores a 9.4.6, se presenta una vulnerabilidad de inyección SQL para todas las instancias del helpdesk. Una explotación de esta vulnerabilidad requiere una cuenta de técnico. • https://github.com/glpi-project/glpi/security/advisories/GHSA-344w-34h9-wwhh • CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') •

CVSS: 7.5EPSS: 31%CPEs: 2EXPL: 2

01 Nov 2019 — GLPI 0.83.7 has Local File Inclusion in common.tabs.php. GLPI versión 0.83.7, presenta una inclusión de archivos locales en el archivo common.tabs.php. • https://www.exploit-db.com/exploits/26366 • CWE-20: Improper Input Validation •

CVSS: 8.8EPSS: 3%CPEs: 1EXPL: 1

25 Sep 2019 — GLPI through 9.4.3 is prone to account takeover by abusing the ajax/autocompletion.php autocompletion feature. The lack of correct validation leads to recovery of the token generated via the password reset functionality, and thus an authenticated attacker can set an arbitrary password for any user. This vulnerability can be exploited to take control of admin account. This vulnerability could be also abused to obtain other sensitive fields like API keys or password hashes. GLPI versiones hasta 9.4.3, es prop... • https://github.com/glpi-project/glpi/security/advisories/GHSA-47hq-pfrr-jh5q • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •

CVSS: 5.4EPSS: 0%CPEs: 1EXPL: 1

15 Jul 2019 — GLPI GLPI Product 9.3.1 is affected by: Cross Site Scripting (XSS). The impact is: All dropdown values are vulnerable to XSS leading to privilege escalation and executing js on admin. The component is: /glpi/ajax/getDropDownValue.php. The attack vector is: 1- User Create a ticket , 2- Admin opens another ticket and click on the "Link Tickets" feature, 3- a request to the endpoint fetches js and executes it. El producto GLPI versión 9.3.1 de GLPI, está afectado por: Cross Site Scripting (XSS). • https://github.com/glpi-project/glpi/blob/9.4/bugfixes/ajax/getDropdownValue.php • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •