Amazon Kindle Fire HD 4.5.5.3 on Fire OS Kernel gcif.c Argument argument injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Amazon Kindle Fire HD 4.5.5.3 on Fire OS. It has been rated as problematic. This issue affects some unknown processing of the file kernel/omap/drivers/misc/gcx/gcioctl/gcif.c of the component Kernel. Performing a manipulation as part of Argument results in argument injection. This vulnerability is cataloged as CVE-2018-11019. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Amazon Kindle Fire HD 4.5.5.3 on Fire OS (Tablet Operating System). It has been classified as problematic. This affects an unknown function of the file kernel/omap/drivers/misc/gcx/gcioctl/gcif.c of the component Kernel. The manipulation as part of a Argument leads to a argument injection vulnerability. CWE is classifying the issue as CWE-88. The product constructs a string for a command to be executed by a separate component
in another control sphere, but it does not properly delimit the
intended arguments, options, or switches within that command string. This is going to have an impact on availability. The summary by CVE is:
kernel/omap/drivers/misc/gcx/gcioctl/gcif.c in the kernel component in Amazon Kindle Fire HD(3rd) Fire OS 4.5.5.3 allows attackers to inject a crafted argument via the argument of an ioctl on device /dev/gcioctl with the command 3221773726 and cause a kernel crash.
The bug was discovered 10/10/2018. The weakness was shared 10/16/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-11019 since 05/13/2018. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-125353, VDB-125352, VDB-125351 and VDB-125350 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: Argument injectionCWE: CWE-88 / 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
05/13/2018 🔍10/10/2018 🔍
10/16/2018 🔍
10/16/2018 🔍
10/17/2018 🔍
04/02/2020 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-11019 (🔍)
GCVE (CVE): GCVE-0-2018-11019
GCVE (VulDB): GCVE-100-125349
See also: 🔍
Entry
Created: 10/17/2018 06:45Updated: 04/02/2020 15:47
Changes: 10/17/2018 06:45 (62), 04/02/2020 15:47 (1)
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.