Comfast CF-XR11 2.7.2 bin/webmgnt sub_41171C protal_delete_picname command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Comfast CF-XR11 2.7.2 and classified as problematic. This affects the function sub_41171C of the file bin/webmgnt. This manipulation of the argument protal_delete_picname causes an unknown weakness.
The identification of this vulnerability is CVE-2023-38864. There is no exploit available.
Details
A vulnerability has been found in Comfast CF-XR11 2.7.2 and classified as problematic. Affected by this vulnerability is the function sub_41171C of the file bin/webmgnt. The manipulation of the argument protal_delete_picname with an unknown input leads to a unknown weakness. The CWE definition for the vulnerability is CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
An issue in COMFAST CF-XR11 v.2.7.2 allows an attacker to execute arbitrary code via the protal_delete_picname parameter in the sub_41171C function at bin/webmgnt.
The weakness was shared 08/16/2023. The advisory is shared at github.com. This vulnerability is known as CVE-2023-38864 since 07/25/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1202 for this issue.
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-42636). 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.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: Command injectionCWE: CWE-77 / CWE-74 / CWE-707
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
07/25/2023 🔍08/16/2023 🔍
08/16/2023 🔍
01/20/2026 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-38864 (🔍)
GCVE (CVE): GCVE-0-2023-38864
GCVE (VulDB): GCVE-100-237289
EUVD: 🔍
Entry
Created: 08/16/2023 07:39Updated: 01/20/2026 07:28
Changes: 08/16/2023 07:39 (38), 09/10/2023 09:29 (12), 01/20/2026 07:28 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.