Open5GS MME up to 2.6.4 S1AP Packet MME_UE_S1AP_ID denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Open5GS MME up to 2.6.4. Affected by this vulnerability is an unknown functionality of the component S1AP Packet Handler. This manipulation of the argument MME_UE_S1AP_ID causes denial of service. This vulnerability appears as CVE-2023-37009. The attack may be initiated remotely. There is no available exploit. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability has been found in Open5GS MME up to 2.6.4 and classified as critical. Affected by this vulnerability is some unknown processing of the component S1AP Packet Handler. The manipulation of the argument MME_UE_S1AP_ID with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability. The summary by CVE is:
Open5GS MME versions <= 2.6.4 contain an assertion that can be remotely triggered via a malformed ASN.1 packet over the S1AP interface. An attacker may send a `Handover Notification` message missing a required `MME_UE_S1AP_ID` field to repeatedly crash the MME, resulting in denial of service.
It is possible to read the advisory at cellularsecurity.org. This vulnerability is known as CVE-2023-37009 since 06/28/2023. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.5
VulDB Base Score: 7.5
VulDB Temp Score: 7.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Denial of serviceCWE: 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/28/2023 🔍01/22/2025 🔍
01/22/2025 🔍
01/22/2025 🔍
Sources
Advisory: cellularsecurity.orgStatus: Not defined
CVE: CVE-2023-37009 (🔍)
GCVE (CVE): GCVE-0-2023-37009
GCVE (VulDB): GCVE-100-292963
Entry
Created: 01/22/2025 04:28 PMUpdated: 01/22/2025 04:31 PM
Changes: 01/22/2025 04:28 PM (17), 01/22/2025 04:29 PM (3), 01/22/2025 04:31 PM (34)
Complete: 🔍
Committer: mitr
Cache ID: 244:0B5:40
No comments yet. Languages: en.
Please log in to comment.