CVE-2020-5248

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. Problem is we can not know which columns or rows in the database are using that; espcially from plugins. Changing the key without updating data would lend in bad password sent from glpi; but storing them again from the UI will work.

• CVE ID
• CVE-2020-5248

• Assigner
• security-advisories@github.com

• Vulnerability Status
• Analyzed

• Published Version
• 2020-05-12T16:15:11

• Last Modified Date
• 2020-05-14T17:08:00

• Version
• 2.0

• Vector String
• AV:N/AC:L/Au:N/C:P/I:N/A:N

• Access Vector
• NETWORK

• Access Compatibility
• LOW

• Authentication
• NONE

• Confidentiality Impact
• PARTIAL

• Integrity Impact
• NONE

• Availability Impact
• NONE

• Base Score
• 5

• Severity
• MEDIUM

• Exploitability Score
• 10

• Impact Score
• 2.9

• Version
• 3.1

• Vector String
• CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

• Attack Vector
• NETWORK

• Attack Compatibility
• LOW

• Privileges Required
• NONE

• User Interaction
• NONE

• Scope
• UNCHANGED

• Confidentiality Impact
• LOW

• Availability Impact
• NONE

• Base Score
• 5.3

• Base Severity
• MEDIUM

• Exploitability Score
• 3.9

• Impact Score
• 1.4