PHICOMM K2 22.5.9.163 autoupgrade.lua autoUpTime input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in PHICOMM K2 22.5.9.163. The affected element is an unknown function in the library /usr/lib/lua/luci/controller/admin/autoupgrade.lua. The manipulation of the argument autoUpTime as part of Shell Metacharacter results in input validation. This vulnerability is reported as CVE-2019-19117. The attack can be launched remotely. No exploit exists.
Details
A vulnerability was found in PHICOMM K2 22.5.9.163. It has been classified as critical. Affected is an unknown part in the library /usr/lib/lua/luci/controller/admin/autoupgrade.lua. The manipulation of the argument autoUpTime as part of a Shell Metacharacter leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
/usr/lib/lua/luci/controller/admin/autoupgrade.lua on PHICOMM K2(PSG1218) V22.5.9.163 devices allows remote authenticated users to execute any command via shell metacharacters in the cgi-bin/luci autoUpTime parameter.
The weakness was disclosed 11/18/2019. This vulnerability is traded as CVE-2019-19117 since 11/18/2019. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is necessary for exploitation. 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
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: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
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/18/2019 🔍11/18/2019 🔍
11/19/2019 🔍
02/23/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2019-19117 (🔍)
GCVE (CVE): GCVE-0-2019-19117
GCVE (VulDB): GCVE-100-145932
Entry
Created: 11/19/2019 06:44Updated: 02/23/2024 15:35
Changes: 11/19/2019 06:44 (37), 11/19/2019 06:49 (17), 02/23/2024 15:35 (3)
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.