What is the severity of CVE-2021-39211?

CVE-2021-39211 is considered a medium severity vulnerability due to the exposure of sensitive GLPI and server information.

How do I fix CVE-2021-39211?

To fix CVE-2021-39211, upgrade GLPI to version 9.5.6 or later or remove the file ajax/telemetry.php as a workaround.

What versions of GLPI are affected by CVE-2021-39211?

CVE-2021-39211 affects GLPI versions from 9.2 to 9.5.5.

What information is disclosed due to CVE-2021-39211?

CVE-2021-39211 allows the telemetry endpoint to disclose sensitive GLPI and server information.

Is there a permanent solution for CVE-2021-39211?

Yes, the permanent solution for CVE-2021-39211 is to update to GLPI version 9.5.6, which includes the fix.

Vulnerability/
CVE-2021-39211

medium

5.3

CWE

200

15/9/2021

4/8/2024

CVE-2021-39211: Disclosure of GLPI and server information in telemetry endpoint

First published: Wed Sep 15 2021(Updated: )

GLPI is a free Asset and IT management software package. Starting in version 9.2 and prior to version 9.5.6, the telemetry endpoint discloses GLPI and server information. This issue is fixed in version 9.5.6. As a workaround, remove the file `ajax/telemetry.php`, which is not needed for usual functions of GLPI.

Credit: security-advisories@github.com

Affected Software	Affected Version	How to fix
Teclib GLPI	>=9.2<9.5.6

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-39211?
CVE-2021-39211 is considered a medium severity vulnerability due to the exposure of sensitive GLPI and server information.
How do I fix CVE-2021-39211?
To fix CVE-2021-39211, upgrade GLPI to version 9.5.6 or later or remove the file ajax/telemetry.php as a workaround.
What versions of GLPI are affected by CVE-2021-39211?
CVE-2021-39211 affects GLPI versions from 9.2 to 9.5.5.
What information is disclosed due to CVE-2021-39211?
CVE-2021-39211 allows the telemetry endpoint to disclose sensitive GLPI and server information.
Is there a permanent solution for CVE-2021-39211?
Yes, the permanent solution for CVE-2021-39211 is to update to GLPI version 9.5.6, which includes the fix.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/title
agent/weakness
agent/author
agent/severity
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/glpi-project
canonical/teclib glpi
version/teclib glpi/9.2

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2021-39211?
CVE-2021-39211 is considered a medium severity vulnerability due to the exposure of sensitive GLPI and server information.
How do I fix CVE-2021-39211?
To fix CVE-2021-39211, upgrade GLPI to version 9.5.6 or later or remove the file ajax/telemetry.php as a workaround.
What versions of GLPI are affected by CVE-2021-39211?
CVE-2021-39211 affects GLPI versions from 9.2 to 9.5.5.
What information is disclosed due to CVE-2021-39211?
CVE-2021-39211 allows the telemetry endpoint to disclose sensitive GLPI and server information.
Is there a permanent solution for CVE-2021-39211?
Yes, the permanent solution for CVE-2021-39211 is to update to GLPI version 9.5.6, which includes the fix.