Skip to content

Pimcore Discloses Usernames In Use

High severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Sep 26, 2023

Package

composer pimcore/pimcore (Composer)

Affected versions

< 6.2.2

Patched versions

6.2.2

Description

Pimcore before 6.2.2 allow attackers to brute-force (guess) valid usernames by using the 'forgot password' functionality as it returns distinct messages for invalid password and non-existing users.

References

Published by the National Vulnerability Database Nov 15, 2019
Published to the GitHub Advisory Database May 24, 2022
Reviewed Jul 18, 2023
Last updated Sep 26, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.105%
(45th percentile)

Weaknesses

CVE ID

CVE-2019-18986

GHSA ID

GHSA-8889-9g3f-73rj

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.