Skip to content

GHSA-8889-9g3f-73rj CVE-2019-18986

Pimcore Discloses Usernames In Use

High Packagist
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.19%
Chance of exploitation in the next 30 days. Higher than 67.88% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-307 Improper Restriction of Excessive Authentication Attempts
Fix
6.2.2
Upgrade pimcore/pimcore to this version or later

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.

Affected versions

Packagist

PackageVulnerableFixed in
pimcore/pimcore
< 6.2.2
6.2.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

pimcore/pimcore Packagist → 6.2.2

composer
composer require pimcore/pimcore:^6.2.2

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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

Weakness

CWE-307: Improper Restriction of Excessive Authentication Attempts

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.

How to prevent it
  • Architecture and Design: Common protection mechanisms include: Disconnecting the user after a small number of failed attempts Implementing a timeout Locking out a targeted account Requiring a computational task on the user's part.
  • Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator. [REF-45]

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-23rh-xw42-fq82
Pimcore: SQL Injection in Custom Reports via Malicious Report Configuration
High Also affects pimcore/pimcore
GHSA-9x44-4gxf-8c25
Pimcore Vulnerable to Remote Code Execution via DataObject Class-Definition Field Name
Critical Also affects pimcore/pimcore
GHSA-w23p-wrp7-ch38
Pimcore Hotspotimage getDataFromResource() unrestricted Serialize::unserialize over object-store column (PHP Object Injection, CWE-502)
Critical Also affects pimcore/pimcore
GHSA-2mhj-fhvg-v428
Pimcore: ClassDefinition UID regex missing end anchor allows SQL injection via Block.php unquoted table name
High Also affects pimcore/pimcore
GHSA-7p36-fq2r-4h7r
Pimcore CMS Twig Sandbox Bypass via SecurityPolicy checkMethodAllowed
High Also affects pimcore/pimcore
GHSA-jwcc-gv4m-93x6
Pimcore has a CustomReports Share Bypass
High Also affects pimcore/pimcore
GHSA-332x-r494-54fq
Pimcore has a WordExport Authorization Bypass for Unauthorized Document Export
Medium Also affects pimcore/pimcore
GHSA-wc7j-g8wx-m2qx
Pimcore: Missing Authorization in WebDAV MOVE via unchecked asset move handling
High Also affects pimcore/pimcore
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor