LiveActive security incident?Get immediate response
CVE Record

CVE-2023-37260: league/oauth2-server key exposed in exception message when passing as string and providing invalid pass phrase

league/oauth2-server is an implementation of an OAuth 2.0 authorization server written in PHP. Starting in version 8.3.2 and prior to version 8.5.3, 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. 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 to receive the patch. As a workaround, pass the key as a file instead of a string.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A PHP OAuth server library could accidentally expose cryptographic key material inside an exception message. This affects league/oauth2-server versions 8.3.2 through before 8.5.3 when keys are passed as strings and an invalid required pass phrase is provided.

Executive priority

Prioritize remediation for any OAuth authorization service using the affected library pattern. The business risk is sensitive key disclosure, which may require credential rotation if historical logs or error outputs exposed the key.

Technical view

CVE-2023-37260 is a CWE-209 information disclosure in the CryptKey constructor. In affected versions, a LogicException could include the provided key string when pass phrase validation failed. The vendor patched this in 8.5.3 so the key is no longer exposed in that exception path.

Likely exposure

Exposure is most likely in PHP applications using league/oauth2-server >=8.3.2 and <8.5.3, passing key material directly as strings to CryptKey, and surfacing exception messages through logs, error responses, monitoring, or support bundles.

Exploitation context

The source bundle does not show known active exploitation, and KEV is false. Risk depends on whether an attacker or unauthorized party can view the exception message. If exposed, the leaked key material could weaken the OAuth server’s trust boundary.

Researcher notes

Evidence is specific to one failure path: invalid required pass phrase plus key passed as a string. The advisory names upgrade 8.5.3 and file-based key passing as the workaround. No source in the bundle confirms weaponized exploitation.

Mitigation direction

  • Upgrade league/oauth2-server to version 8.5.3 or later.
  • Pass keys as files instead of strings when using CryptKey.
  • Review vendor advisory and release notes before deployment.
  • Limit exposure of exception details in user-facing responses and shared logs.

Validation and detection

  • Inventory applications using league/oauth2-server.
  • Confirm installed versions are not >=8.3.2 and <8.5.3.
  • Check whether CryptKey receives key strings rather than file paths.
  • Review error logs for exposed key material from LogicException messages.
  • Verify production error handling does not disclose exception details publicly.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-209: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-37260 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2023-37260Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
thephpleagueoauth2-server>= 8.3.2, < 8.5.3Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-209 · source CWE mapping

Generation of Error Message Containing Sensitive Information

Generation of Error Message Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.