CVE-2019-9121
Motorola Command Injection Vulnerability Allows Remote Code Execution
Description
An issue was discovered on Motorola C1 and M2 devices with firmware 1.01 and 1.07 respectively. This issue is a Command Injection allowing a remote attacker to execute arbitrary code, and get a root shell. A command Injection vulnerability allows attackers to execute arbitrary OS commands via a crafted /HNAP1 POST request. This occurs when any HNAP API function triggers a call to the system function with untrusted input from the request body for the SetSmartQoSSettings API function, as demonstrated by shell metacharacters in the smartqos_priority_devices field.
INFO
Published Date :
March 7, 2019, 11:29 p.m.
Last Modified :
Nov. 21, 2024, 4:51 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.9
Exploitability Score :
3.9
Public PoC/Exploit Available at Github
CVE-2019-9121 has a 2 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
Affected Products
The following products are affected by CVE-2019-9121
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2019-9121.
| URL | Resource |
|---|---|
| https://github.com/lieanu/vuls/blob/master/motorola/M2_C1/SetSmartQoSSettings.md | Issue Tracking Third Party Advisory |
| https://github.com/lieanu/vuls/blob/master/motorola/M2_C1/SetSmartQoSSettings.md | Issue Tracking Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Some Vuls.
Some Vuls.
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2019-9121 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2019-9121 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://github.com/lieanu/vuls/blob/master/motorola/M2_C1/SetSmartQoSSettings.md -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CWE Remap by [email protected]
Aug. 24, 2020
Action Type Old Value New Value Changed CWE CWE-77 CWE-78 -
Initial Analysis by [email protected]
Mar. 08, 2019
Action Type Old Value New Value Added CVSS V2 (AV:N/AC:L/Au:N/C:C/I:C/A:C) Added CVSS V3 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://github.com/lieanu/vuls/blob/master/motorola/M2_C1/SetSmartQoSSettings.md No Types Assigned https://github.com/lieanu/vuls/blob/master/motorola/M2_C1/SetSmartQoSSettings.md Issue Tracking, Third Party Advisory Added CWE CWE-77 Added CPE Configuration AND OR *cpe:2.3:o:motorola:m2_firmware:1.07:*:*:*:*:*:*:* OR cpe:2.3:h:motorola:m2:-:*:*:*:*:*:*:* Added CPE Configuration AND OR *cpe:2.3:o:motorola:c1_firmware:1.01:*:*:*:*:*:*:* OR cpe:2.3:h:motorola:c1:-:*:*:*:*:*:*:*
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2019-9121 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2019-9121
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.41 }} 0.08%
score
0.73551
percentile