API Platform up to 4.0.21 isCacheKeySafe incorrect behavior order
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in API Platform up to 4.0.21. Affected is the function ItemNormalizer::isCacheKeySafe. Performing a manipulation results in incorrect behavior order.
This vulnerability is identified as CVE-2025-31485. The attack can be initiated remotely. There is not any exploit available.
You should upgrade the affected component.
Details
A vulnerability classified as problematic has been found in API Platform up to 4.0.21. This affects the function ItemNormalizer::isCacheKeySafe. The manipulation with an unknown input leads to a incorrect behavior order vulnerability. CWE is classifying the issue as CWE-696. The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways which may produce resultant weaknesses. This is going to have an impact on confidentiality. The summary by CVE is:
API Platform Core is a system to create hypermedia-driven REST and GraphQL APIs. Prior to 4.0.22, a GraphQL grant on a property might be cached with different objects. The ApiPlatform\GraphQl\Serializer\ItemNormalizer::isCacheKeySafe() method is meant to prevent the caching but the parent::normalize method that is called afterwards still creates the cache key and causes the issue. This vulnerability is fixed in 4.0.22.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-31485 since 03/28/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 4.0.22 eliminates this vulnerability. Applying the patch 7af65aad13037d7649348ee3dcd88e084ef771f8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
- 4.0.0
- 4.0.1
- 4.0.2
- 4.0.3
- 4.0.4
- 4.0.5
- 4.0.6
- 4.0.7
- 4.0.8
- 4.0.9
- 4.0.10
- 4.0.11
- 4.0.12
- 4.0.13
- 4.0.14
- 4.0.15
- 4.0.16
- 4.0.17
- 4.0.18
- 4.0.19
- 4.0.20
- 4.0.21
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub_M): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Incorrect behavior orderCWE: CWE-696
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: API Platform 4.0.22
Patch: 7af65aad13037d7649348ee3dcd88e084ef771f8
Timeline
03/28/2025 🔍04/04/2025 🔍
04/04/2025 🔍
04/04/2025 🔍
Sources
Advisory: GHSA-428q-q3vv-3fq3Status: Confirmed
CVE: CVE-2025-31485 (🔍)
GCVE (CVE): GCVE-0-2025-31485
GCVE (VulDB): GCVE-100-303291
Entry
Created: 04/04/2025 07:16Changes: 04/04/2025 07:16 (66)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.