Google Android SDK up to M5-rc14 bmp::readfromstream numeric error
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in Google Android SDK up to M5-rc14. This vulnerability affects the function bmp::readfromstream. The manipulation results in numeric error.
This vulnerability is reported as CVE-2008-0986. Moreover, an exploit is present.
Details
A vulnerability was found in Google Android SDK up to M5-rc14 (Smartphone Operating System). It has been classified as critical. Affected is the function bmp::readfromstream. The manipulation with an unknown input leads to a numeric error vulnerability. CWE is classifying the issue as CWE-189. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Integer overflow in the BMP::readFromStream method in the libsgl.so library in Google Android SDK m3-rc37a and earlier, and m5-rc14, allows remote attackers to execute arbitrary code via a crafted BMP file with a header containing a negative offset field.
The weakness was disclosed 03/05/2008 by Alfredo Ortega with CORE Security Technologies (Website). The advisory is shared for download at securityfocus.com. This vulnerability is traded as CVE-2008-0986 since 02/26/2008. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details and a public exploit are known.
The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept. As 0-day the estimated underground price was around $100k and more.
The vulnerability is also documented in the databases at X-Force (40999), Exploit-DB (31308) and SecurityFocus (BID 28006†). The entry VDB-41351 is pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Numeric errorCWE: CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/26/2008 🔍03/04/2008 🔍
03/05/2008 🔍
03/05/2008 🔍
03/16/2015 🔍
06/08/2024 🔍
Sources
Vendor: google.comAdvisory: securityfocus.com⛔
Researcher: Alfredo Ortega
Organization: CORE Security Technologies
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2008-0986 (🔍)
GCVE (CVE): GCVE-0-2008-0986
GCVE (VulDB): GCVE-100-41352
X-Force: 40999 - Android SDK BMP::readFromStream method integer overflow
SecurityFocus: 28006 - Android Web Browser BMP File Integer Overflow Vulnerability
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 03/16/2015 13:43Updated: 06/08/2024 13:38
Changes: 03/16/2015 13:43 (61), 11/10/2017 13:56 (1), 06/08/2024 13:38 (17)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.