Akamai Rate Control incorrect provision of specified functionality
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Akamai Rate Control. Impacted is an unknown function. Such manipulation leads to incorrect provision of specified functionality. This vulnerability is traded as CVE-2025-54568. The attack may be launched remotely. There is no exploit available. This product is a managed service, which means users themselves cannot handle vulnerability countermeasures.
Details
A vulnerability was found in Akamai Rate Control (affected version not known). It has been rated as problematic. Affected by this issue is some unknown functionality. The manipulation with an unknown input leads to a incorrect provision of specified functionality vulnerability. Using CWE to declare the problem leads to CWE-684. The code does not function according to its published specifications, potentially leading to incorrect usage. Impacted is availability. CVE summarizes:
Akamai Rate Control alpha before 2025 allows attackers to send requests above the stipulated thresholds because the rate is measured separately for each edge node.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-54568 since 07/25/2025. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Managed Service
- yes
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.7
CNA Vector (MITRE): 🔒
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 provision of specified functionalityCWE: CWE-684
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
Status: 🔍0-Day Time: 🔒
Timeline
07/25/2025 Advisory disclosed07/25/2025 CVE reserved
07/25/2025 VulDB entry created
07/25/2025 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2025-54568 (🔒)
GCVE (CVE): GCVE-0-2025-54568
GCVE (VulDB): GCVE-100-317564
Entry
Created: 07/25/2025 08:43Changes: 07/25/2025 08:43 (60)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.