CVE-2011-2720: Infoleak

Published Jul 27, 2011
·
Updated

It was found that GLPI, the Information Resource-Manager with an additional Administration-Interface, did not properly blacklist certain sensitive variables (like GLPI username and password). A remote attacker could use this flaw to obtain access to plaintext form of these values via specially-crafted HTTP POST request.

References: [1] http://www.glpi-project.org/spip.php?page=annonce&idbreve=237&lang=en [2] https://forge.indepnet.net/projects/glpi/versions/605 [3] https://forge.indepnet.net/issues/3017

Relevant patches: [4] https://forge.indepnet.net/projects/glpi/repository/revisions/14951 [5] https://forge.indepnet.net/projects/glpi/repository/revisions/14952 [6] https://forge.indepnet.net/projects/glpi/repository/revisions/14954 [7] https://forge.indepnet.net/projects/glpi/repository/revisions/14955 [8] https://forge.indepnet.net/projects/glpi/repository/revisions/14956 [9] https://forge.indepnet.net/projects/glpi/repository/revisions/14957 [10] https://forge.indepnet.net/projects/glpi/repository/revisions/14958 [11] https://forge.indepnet.net/projects/glpi/repository/revisions/14960 [12] https://forge.indepnet.net/projects/glpi/repository/revisions/14966

Other sources

The autocompletion functionality in GLPI before 0.80.2 does not blacklist certain username and password fields, which allows remote attackers to obtain sensitive information via a crafted POST request.

MITRE

Affected Software

52 affected components
GLPI-PROJECT GLPI=0.72.4
GLPI-PROJECT GLPI=0.72-rc1
GLPI-PROJECT GLPI=0.72.1
GLPI-PROJECT GLPI=0.72.2
GLPI-PROJECT GLPI=0.70-rc2
GLPI-PROJECT GLPI=0.70.1
GLPI-PROJECT GLPI=0.6-rc3
GLPI-PROJECT GLPI=0.71.5
GLPI-PROJECT GLPI=0.68.2
GLPI-PROJECT GLPI=0.5-rc1
GLPI-PROJECT GLPI=0.71.3
GLPI-PROJECT GLPI=0.70
GLPI-PROJECT GLPI=0.72-rc2
GLPI-PROJECT GLPI=0.71
GLPI-PROJECT GLPI=0.71.1-rc2
GLPI-PROJECT GLPI=0.72
GLPI-PROJECT GLPI=0.6-rc2
GLPI-PROJECT GLPI=0.70-rc3
GLPI-PROJECT GLPI=0.71.1-rc3
GLPI-PROJECT GLPI=0.78.2
GLPI-PROJECT GLPI=0.68
GLPI-PROJECT GLPI=0.72-rc3
GLPI-PROJECT GLPI=0.5
GLPI-PROJECT GLPI<=0.80.1
GLPI-PROJECT GLPI=0.71.2
GLPI-PROJECT GLPI=0.70-rc1
GLPI-PROJECT GLPI=0.71.4
GLPI-PROJECT GLPI=0.51
GLPI-PROJECT GLPI=0.65-rc2
GLPI-PROJECT GLPI=0.68.3
GLPI-PROJECT GLPI=0.65-rc1
GLPI-PROJECT GLPI=0.78.3
GLPI-PROJECT GLPI=0.68-rc1
GLPI-PROJECT GLPI=0.78.4
GLPI-PROJECT GLPI=0.51a
GLPI-PROJECT GLPI=0.78.1
GLPI-PROJECT GLPI=0.71.1
GLPI-PROJECT GLPI=0.6
GLPI-PROJECT GLPI=0.72.3
GLPI-PROJECT GLPI=0.71.6
GLPI-PROJECT GLPI=0.6-rc1
GLPI-PROJECT GLPI=0.68-rc3
GLPI-PROJECT GLPI=0.68.1
GLPI-PROJECT GLPI=0.71.1-rc1
GLPI-PROJECT GLPI=0.68-rc2
GLPI-PROJECT GLPI=0.5-rc2
GLPI-PROJECT GLPI=0.65
GLPI-PROJECT GLPI=0.78.5
GLPI-PROJECT GLPI=0.80
GLPI-PROJECT GLPI=0.42
GLPI-PROJECT GLPI=0.70.2
GLPI-PROJECT GLPI=0.78

Event History

Jul 27, 2011
Data Sourced
via Red Hat·07:00 PM
DescriptionSeverityAffected Software
Aug 5, 2011
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2011-2720?

CVE-2011-2720 is considered to be a medium severity vulnerability due to its potential exposure of sensitive information.

2

How do I fix CVE-2011-2720?

To fix CVE-2011-2720, upgrade GLPI to a version later than 0.80.1, which addresses the sensitive variable blacklisting issue.

3

What does CVE-2011-2720 affect?

CVE-2011-2720 affects multiple versions of GLPI, specifically versions up to and including 0.80.1.

4

Can CVE-2011-2720 allow unauthorized access?

Yes, CVE-2011-2720 can allow remote attackers to access sensitive GLPI credentials in plaintext.

5

Is there a specific GLPI version that is vulnerable to CVE-2011-2720?

Yes, CVE-2011-2720 affects GLPI versions from 0.5 to 0.80.1, inclusive.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203