Skip to content

ezplatform-graphql GraphQL queries can expose password hashes

High severity GitHub Reviewed Published Nov 10, 2022 in ezsystems/ezplatform-graphql • Updated Jan 31, 2023

Package

composer ezsystems/ezplatform-graphql (Composer)

Affected versions

>= 1.0.0-rc1, < 1.0.13
>= 2.0.0-beta1, < 2.3.12

Patched versions

1.0.13
2.3.12

Description

Impact

Unauthenticated GraphQL queries for user accounts can expose password hashes of users that have created or modified content, typically but not necessarily limited to administrators and editors.

Patches

Resolving versions: Ibexa DXP v1.0.13, v2.3.12

Workarounds

Remove the "passwordHash" entry from "src/bundle/Resources/config/graphql/User.types.yaml" in the GraphQL package, and other properties like hash type, email, login if you prefer.

References

This issue was reported to us by Philippe Tranca ("trancap") of the company Lexfo. We are very grateful for their research, and responsible disclosure to us of this critical vulnerability.

For more information

If you have any questions or comments about this advisory, please contact Support via your service portal.

References

@glye glye published to ezsystems/ezplatform-graphql Nov 10, 2022
Published by the National Vulnerability Database Nov 10, 2022
Published to the GitHub Advisory Database Nov 10, 2022
Reviewed Nov 10, 2022
Last updated Jan 31, 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
High
Integrity
None
Availability
None

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:H/I:N/A:N

EPSS score

0.056%
(25th percentile)

Weaknesses

CVE ID

CVE-2022-41876

GHSA ID

GHSA-c7pc-pgf6-mfh5

Source code

Credits

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