# CVE-2015-8096: Integer overflow in n/a

> Remote attackers can execute arbitrary code via integer overflow in Google Picasa, requiring user interaction to open malicious files.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hcvg-vqp3-m7mq

## What is CVE-2015-8096?

CVE-2015-8096 is a critical vulnerability in n/a, published on 9 Nov 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-189, CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2015-8096?

It affects 1 product.


Products: Google Picasa.

## How do I fix CVE-2015-8096?

No fix has been published for CVE-2015-8096 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-8096 being exploited?

There is no known exploitation of CVE-2015-8096 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-8221](https://insights.sbomify.com/CVE-2015-8221/): Integer overflow in n/a (critical 10.0)
- [CVE-2011-2747](https://insights.sbomify.com/CVE-2011-2747/): Code injection in n/a (critical 9.3)
- [CVE-2013-5349](https://insights.sbomify.com/CVE-2013-5349/): Integer overflow in n/a (high 7.5)
- [CVE-2013-5357](https://insights.sbomify.com/CVE-2013-5357/): Integer overflow in n/a (high 7.5)
- [CVE-2013-5358](https://insights.sbomify.com/CVE-2013-5358/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-8096 and fix it if it is affected.

What it is: CVE-2015-8096 is a critical vulnerability in n/a, published on 9 Nov 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-8096 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-8096/ (Markdown: https://insights.sbomify.com/CVE-2015-8096/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-8096
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-8096
- OSV: https://osv.dev/vulnerability/CVE-2015-8096

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-8096/
Summaries are generated and may contain mistakes; the official description above is the record.