Phicomm FIR151B A2/FIR302E A2/FIR300B A2/FIR303B A2 up to 3.0.1.17 tracert trHops privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Phicomm FIR151B A2, FIR302E A2, FIR300B A2 and FIR303B A2 up to 3.0.1.17. This affects the function tracert. Executing a manipulation of the argument trHops can lead to an unknown weakness.
The identification of this vulnerability is CVE-2022-37777. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability has been found in Phicomm FIR151B A2, FIR302E A2, FIR300B A2 and FIR303B A2 up to 3.0.1.17 and classified as critical. The manipulation of the argument trHops with an unknown input leads to a unknown weakness. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Phicomm FIR151B A2, FIR302E A2, FIR300B A2, FIR303B A2 routers 3.0.1.17 and earlier were discovered to contain a remote command execution (RCE) vulnerability via the trHops parameter of the tracert function.
The weakness was shared 09/08/2022. The advisory is shared for download at github.com. This vulnerability was named CVE-2022-37777 since 08/08/2022. There are known technical details, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
- 3.0.1.0
- 3.0.1.1
- 3.0.1.2
- 3.0.1.3
- 3.0.1.4
- 3.0.1.5
- 3.0.1.6
- 3.0.1.7
- 3.0.1.8
- 3.0.1.9
- 3.0.1.10
- 3.0.1.11
- 3.0.1.12
- 3.0.1.13
- 3.0.1.14
- 3.0.1.15
- 3.0.1.16
- 3.0.1.17
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
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: Privilege escalationCWE: 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
08/08/2022 🔍09/08/2022 🔍
09/08/2022 🔍
10/14/2022 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2022-37777 (🔍)
GCVE (CVE): GCVE-0-2022-37777
GCVE (VulDB): GCVE-100-208084
Entry
Created: 09/08/2022 09:44Updated: 10/14/2022 11:04
Changes: 09/08/2022 09:44 (37), 10/14/2022 11:04 (11)
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.