Phicomm FIR151B A2/FIR302E A2/FIR300B A2/FIR303B A2 3.0.1.17 time current_time privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Phicomm FIR151B A2, FIR302E A2, FIR300B A2 and FIR303B A2 3.0.1.17 and classified as critical. This impacts the function Time. The manipulation of the argument current_time leads to an unknown weakness.
This vulnerability is referenced as CVE-2022-37778. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Phicomm FIR151B A2, FIR302E A2, FIR300B A2 and FIR303B A2 3.0.1.17 and classified as critical. The manipulation of the argument current_time with an unknown input leads to a unknown weakness. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Phicomm FIR151B A2, FIR302E A2, FIR300B A2, FIR303B A2 routers V3.0.1.17 were discovered to contain a remote command execution (RCE) vulnerability via the current_time parameter of the time function.
The weakness was published 09/08/2022. The advisory is shared at github.com. The identification of this vulnerability is CVE-2022-37778 since 08/08/2022. Technical details are known, 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.
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: 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-37778 (🔍)
GCVE (CVE): GCVE-0-2022-37778
GCVE (VulDB): GCVE-100-208085
Entry
Created: 09/08/2022 10:10Updated: 10/14/2022 11:09
Changes: 09/08/2022 10:10 (37), 10/14/2022 11:09 (11)
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.