Ruijie EG up to EG_3.0(1)B11P216 Filter Remote Code Execution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Ruijie EG up to EG_3.0(1)B11P216. This issue affects some unknown processing of the component Filter. Performing a manipulation results in an unknown weakness. This vulnerability was named CVE-2023-48849. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as critical, was found in Ruijie EG up to EG_3.0(1)B11P216. This affects some unknown functionality of the component Filter. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Ruijie EG Series Routers version EG_3.0(1)B11P216 and before allows unauthenticated attackers to remotely execute arbitrary code due to incorrect filtering.
The weakness was presented 12/06/2023. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-48849 since 11/20/2023. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-52879). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
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: Remote Code ExecutionCWE: Unknown
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
11/20/2023 🔍12/06/2023 🔍
12/06/2023 🔍
03/02/2026 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-48849 (🔍)
GCVE (CVE): GCVE-0-2023-48849
GCVE (VulDB): GCVE-100-247053
EUVD: 🔍
Entry
Created: 12/06/2023 09:37Updated: 03/02/2026 03:07
Changes: 12/06/2023 09:37 (36), 12/30/2023 07:29 (11), 03/02/2026 03:07 (15)
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.