# CVE-2007-4823: Memory corruption in n/a

> Multiple buffer overflows in Google Picasa allow attackers to execute arbitrary code or cause denial of service via unspecified vectors.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 11 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xq75-f84r-j89w

## What is CVE-2007-4823?

CVE-2007-4823 is a high-severity memory corruption vulnerability in n/a, published on 11 Sep 2007. 

### Official description

Multiple buffer overflows in Google Picasa have unspecified attack vectors and impact.  NOTE: this information is based upon a vague pre-advisory.

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

## Which versions are affected by CVE-2007-4823?

It affects 1 product.


Products: Google Picasa.

## How do I fix CVE-2007-4823?

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

## Is CVE-2007-4823 being exploited?

There is no known exploitation of CVE-2007-4823 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-2015-8096](https://insights.sbomify.com/CVE-2015-8096/): 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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4823 and fix it if it is affected.

What it is: CVE-2007-4823 is a high-severity memory corruption vulnerability in n/a, published on 11 Sep 2007. 
Exploitation: There is no known exploitation of CVE-2007-4823 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-2007-4823/ (Markdown: https://insights.sbomify.com/CVE-2007-4823/index.md)
```

## Sources

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

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