Skip to content

API Platform Core can leak exceptions message that may contain sensitive information

Moderate severity GitHub Reviewed Published Apr 3, 2025 in api-platform/core • Updated Apr 4, 2025

Package

composer api-platform/core (Composer)

Affected versions

>= 3.2.0, < 3.2.5

Patched versions

3.2.5

Description

Summary

Exception messages, that are not HTTP exceptions, are visible in the JSON error response.

Details

While we wanted to make our errors compatible with the JSON Problem specification, we ended up handling more exceptions then we did previously (introduced at api-platform/core#5823). Instead of leaving that to Symfony, we ended up serializing errors with our normalizers which lead to not hiding the exception details. Note that the trace is hidden in production but the message is not, and the message can contain sensitive information.

PoC

At https://github.com/ili101/api-platform/tree/test3.2 it triggers an authentication exception as LDAP is not reachable. You can find the message available as a JSON response when trying to reach an endpoint.

Impact

Version 3.2 until 3.2.4 is impacted.

References

@soyuka soyuka published to api-platform/core Apr 3, 2025
Published to the GitHub Advisory Database Apr 3, 2025
Reviewed Apr 3, 2025
Published by the National Vulnerability Database Apr 3, 2025
Last updated Apr 4, 2025

Severity

Moderate

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

EPSS score

Weaknesses

CVE ID

CVE-2023-47639

GHSA ID

GHSA-rfw5-cqjj-7v9r

Source code

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