Picasa vulnerabilitiesRanked by how likely they are to be used.
Picasa is made by Google. We track 11 published vulnerabilities in it, across 13 versions. None of them is on the list of flaws known to be exploited today. If you run Picasa, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Picasa vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Picasa's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Picasa flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 4.3%CVE-2011-2747Critical
Google Picasa before 3.6 Build 105.67 does not properly handle invalid properties in JPEG images, which allows remote attackers to execute arbitrary code via a crafted image file.
- 4.0%CVE-2015-8096Critical
Integer overflow in Google Picasa 3.9.140 Build 239 and Build 248 allows remote attackers to execute arbitrary code via unspecified vectors related to "phase one 0x412 tag," which triggers a heap-based buffer overflow.
- 4.0%CVE-2015-8221Critical
Integer overflow in Google Picasa before 3.9.140 Build 259 allows remote attackers to execute arbitrary code via the CAMF section in a FOVb image, which triggers a heap-based buffer overflow.
- 2.3%CVE-2013-5349High
Integer underflow in Picasa3.exe in Google Picasa before 3.9.0 Build 137.69 allows remote attackers to execute arbitrary code via a crafted JPEG tag that triggers a heap-based buffer overflow, as demonstrated using a...
- 2.3%CVE-2013-5357High
Integer overflow in Picasa3.exe in Google Picasa before 3.9.0 Build 137.69 allows remote attackers to execute arbitrary code via a long TIFF tag that triggers a heap-based buffer overflow, as demonstrated using a...
- 2.3%CVE-2013-5359High
Stack-based buffer overflow in Picasa3.exe in Google Picasa before 3.9.0 Build 137.69 might allow remote attackers to execute arbitrary code via a crafted RAW file, as demonstrated using a KDC file with a certain size.
- 1.3%CVE-2013-5358High
Picasa3.exe in Google Picasa before 3.9.0 Build 137.69 allows remote attackers to trigger memory corruption via a crafted TIFF tag, as demonstrated using a KDC file with a DSLR-A100 model and certain sequences of tags.
- 0.5%CVE-2007-4847Medium
Google Picasa allows remote attackers to read image files stored by Picasa via unspecified vectors involving a picasa:// URI.
- 0.5%CVE-2007-4823High
Multiple buffer overflows in Google Picasa have unspecified attack vectors and impact.
- 0.4%CVE-2007-4824Medium
Multiple cross-application scripting (XAS) vulnerabilities in Google Picasa have unspecified attack vectors and impact.
Running Picasa? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Google Picasa before 3.6 Build 105.67 does not properly handle invalid properties in JPEG images, which allows remote attackers to execute arbitrary code via a crafted image file.
- Matched to
- Picasa on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 11 published vulnerabilities listed under the name Picasa, across 13 versions.
None of Picasa's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Picasa. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.