Skip to content

league/oauth2-server key exposed in exception message when passing as a string and providing an invalid pass phrase

High severity GitHub Reviewed Published Jul 6, 2023 in thephpleague/oauth2-server • Updated Nov 5, 2023

Package

composer league/oauth2-server (Composer)

Affected versions

>= 8.3.2, < 8.4.2
>= 8.5.0, < 8.5.3

Patched versions

8.4.2
8.5.3

Description

Impact

Servers that passed their keys to the CryptKey constructor as as string instead of a file path will have had that key included in a LogicException message if they did not provide a valid pass phrase for the key where required.

Patches

This issue has been patched so that the provided key is no longer exposed in the exception message in the scenario outlined above. Users should upgrade to version 8.5.3 or 8.4.2 to receive the patch.

Workarounds

We recommend upgrading the oauth2-server to one of the patched releases (8.5.3 or 8.4.2). If you are unable to upgrade you can avoid this security issue by passing your key as a file instead of a string.

References

References

@Sephster Sephster published to thephpleague/oauth2-server Jul 6, 2023
Published by the National Vulnerability Database Jul 6, 2023
Published to the GitHub Advisory Database Jul 6, 2023
Reviewed Jul 6, 2023
Last updated Nov 5, 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
Low
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:L/A:N

EPSS score

0.109%
(45th percentile)

Weaknesses

CVE ID

CVE-2023-37260

GHSA ID

GHSA-wj7q-gjg8-3cpm

Source code

Credits

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