Google Android up to 8.1 avrc_pars_tg.cc avrc_pars_vendor_cmd memory corruption

Summaryinfo

A vulnerability marked as critical has been reported in Google Android up to 8.1. The impacted element is the function avrc_pars_vendor_cmd of the file avrc_pars_tg.cc. Performing a manipulation results in memory corruption. This vulnerability is cataloged as CVE-2017-13267. It is possible to initiate the attack remotely. There is no exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability classified as critical has been found in Google Android up to 8.1 (Smartphone Operating System). This affects the function avrc_pars_vendor_cmd of the file avrc_pars_tg.cc. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In avrc_pars_vendor_cmd of avrc_pars_tg.cc, there is a possible stack corruption due to a missing bounds check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1. Android ID: A-69479009.

The bug was discovered 04/04/2018. The weakness was shared 04/04/2018 (Website). The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2017-13267 since 08/23/2017. 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. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 01/21/2020). It is expected to see the exploit prices for this product increasing in the near future.

Applying a patch is able to eliminate this problem.

The entries VDB-83180, VDB-115633, VDB-115638 and VDB-115639 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Smartphone Operating System

Vendor

• Google

Name

• Android

Version

• 6.0
• 6.0.1
• 7.0
• 7.1.1
• 7.1.2
• 8.0
• 8.1

License

• free

Website

• Vendor: https://www.google.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion