LG Optimus/Mach/Prada/Lollipop Backup memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.7$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in LG Optimus, Mach, Prada and Lollipop. This vulnerability affects unknown code of the component Backup. This manipulation causes memory corruption. This vulnerability is registered as CVE-2013-3685. Furthermore, an exploit is available.

Detailsinfo

A vulnerability has been found in LG Optimus, Mach, Prada and Lollipop (the affected version is unknown) and classified as critical. Affected by this vulnerability is an unknown code of the component Backup. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was published 06/24/2013 by Justin Case with Google Chrome Security Team as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. The public release happened without involvement of LG. This vulnerability is known as CVE-2013-3685 since 05/28/2013. The exploitation appears to be difficult. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available.

After immediately, there has been an exploit disclosed. It is possible to download the exploit at github.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k.

The problem might be mitigated by replacing the product with Apple iPhone as an alternative.

The vulnerability is also documented in the vulnerability database at OSVDB (94524†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.2
VulDB Meta Temp Score: 7.9

VulDB Base Score: 9.3
VulDB Temp Score: 8.8
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.0
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Alternative: Apple iPhone

Timelineinfo

05/28/2013 🔍
06/24/2013 +27 days 🔍
06/24/2013 +0 days 🔍
06/25/2013 +1 days 🔍
05/17/2021 +2883 days 🔍

Sourcesinfo

Advisory: seclists.org
Researcher: Justin Case
Organization: Google Chrome Security Team
Status: Not defined

CVE: CVE-2013-3685 (🔍)
GCVE (CVE): GCVE-0-2013-3685
GCVE (VulDB): GCVE-100-9265
X-Force: 85296
OSVDB: 94524

scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 06/25/2013 15:41
Updated: 05/17/2021 11:14
Changes: 06/25/2013 15:41 (48), 03/19/2019 15:21 (2), 05/17/2021 11:08 (3), 05/17/2021 11:14 (18)
Complete: 🔍
Committer:
Cache ID: 216:F6C:103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!