Google Picasa 3.9.0 Build 3.9.12.24/3.9.0 Build 136.09 biBitCount memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Google Picasa 3.9.0 Build 3.9.12.24/3.9.0 Build 136.09 and classified as critical. Affected by this issue is some unknown functionality of the component biBitCount. This manipulation causes memory corruption. There is no available exploit. The affected component should be upgraded.
Details
A vulnerability was found in Google Picasa 3.9.0 Build 3.9.12.24/3.9.0 Build 136.09. It has been declared as very critical. Affected by this vulnerability is an unknown part of the component biBitCount. 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 presented 03/14/2013 by Kaveh Ghaemmaghami (coolkaveh) as confirmed changelog entry (Website) via Secunia. The advisory is shared at support.google.com. The public release was coordinated in cooperation with Google. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/04/2018).
Upgrading to version 3.9.0 Build 136.17 or 3.9.0 Build 3.9.14.34 eliminates this vulnerability. The upgrade is hosted for download at support.google.com. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at OSVDB (91508†), Secunia (SA51652†) and SecurityTracker (ID 1028324†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
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: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
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: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Picasa 3.9.0 Build 136.17/3.9.0 Build 3.9.14.34
Timeline
03/14/2013 🔍03/14/2013 🔍
03/20/2013 🔍
03/21/2013 🔍
03/25/2013 🔍
05/04/2018 🔍
Sources
Vendor: google.comAdvisory: support.google.com
Researcher: Kaveh Ghaemmaghami (coolkaveh)
Status: Confirmed
Coordinated: 🔍
GCVE (VulDB): GCVE-100-8053
Secunia: 51652 - Google Picasa BMP and TIFF Images Processing Vulnerabilities, Highly Critical
OSVDB: 91508
SecurityTracker: 1028324
Entry
Created: 03/25/2013 10:38Updated: 05/04/2018 09:12
Changes: 03/25/2013 10:38 (53), 05/04/2018 09:12 (1)
Complete: 🔍
Committer:
Cache ID: 216:FCD: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.