org.eclipse.milo:sdk-server up to 0.6.7 CloseSession Request deleteSubscription memory allocation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.7 | $0-$5k | 0.00 |
Summary
A vulnerability was found in org.eclipse.milo:sdk-server up to 0.6.7. It has been rated as problematic. This affects an unknown function of the component CloseSession Request Handler. This manipulation of the argument deleteSubscription causes memory allocation. This vulnerability is tracked as CVE-2022-25897. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in org.eclipse.milo:sdk-server up to 0.6.7. Affected by this vulnerability is an unknown function of the component CloseSession Request Handler. The manipulation of the argument deleteSubscription with an unknown input leads to a memory allocation vulnerability. The CWE definition for the vulnerability is CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. As an impact it is known to affect availability. The summary by CVE is:
The package org.eclipse.milo:sdk-server before 0.6.8 are vulnerable to Denial of Service (DoS) when bypassing the limitations for excessive memory consumption by sending multiple CloseSession requests with the deleteSubscription parameter equal to False.
The weakness was disclosed 09/08/2022 as 1030. The advisory is shared at github.com. This vulnerability is known as CVE-2022-25897 since 02/24/2022. Technical details are known, but no exploit is available.
Upgrading to version 0.6.8 eliminates this vulnerability. Applying the patch 4534381760d7d9f0bf00cbf6a8449bb0d13c6ce5 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.9
CNA Vector (Snyk): 🔍
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: Memory allocationCWE: CWE-789 / CWE-400 / CWE-404
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: org.eclipse.milo:sdk-server 0.6.8
Patch: 4534381760d7d9f0bf00cbf6a8449bb0d13c6ce5
Timeline
02/24/2022 🔍09/08/2022 🔍
09/08/2022 🔍
09/08/2022 🔍
Sources
Advisory: 1030Status: Confirmed
CVE: CVE-2022-25897 (🔍)
GCVE (CVE): GCVE-0-2022-25897
GCVE (VulDB): GCVE-100-208117
Entry
Created: 09/08/2022 13:54Changes: 09/08/2022 13:54 (53)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.