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

> Remote attackers can execute arbitrary code via a heap-based buffer overflow in the viewer ActiveX control of Sony Network Cameras.

- **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:** 29 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xh77-g4qv-rh25

## What is CVE-2007-3488?

CVE-2007-3488 is a critical memory corruption vulnerability in n/a, published on 29 Jun 2007. 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

Heap-based buffer overflow in the viewer ActiveX control in Sony Network Camera SNC-RZ25N before 1.30; SNC-P1 and SNC-P5 before 1.29; SNC-CS10 and SNC-CS11 before 1.06; SNC-DF40N and SNC-DF70N before 1.18; SNC-RZ50N and SNC-CS50N before 2.22; SNC-DF85N, SNC-DF80N, and SNC-DF50N before 1.12; and SNC-RX570N/W, SNC-RX570N/B, SNC-RX550N/W, SNC-RX550N/B, SNC-RX530N/W, and SNC-RX530N/B 3.00 and 2.x before 2.31; allows remote attackers to execute arbitrary code via a long first argument to the PrmSetNetworkParam method.

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

It affects 1 product.


Products: Sony Sony Network Camera Snc-P5.

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

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

## Is CVE-2007-3488 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-3488 exists.

Public exploit code:

- Sony Network Camera SNC-P5 1.0 - ActiveX viewer Heap Overflow (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3488 is a critical memory corruption vulnerability in n/a, published on 29 Jun 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-3488 exists.

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-3488/ (Markdown: https://insights.sbomify.com/CVE-2007-3488/index.md)
```

## Sources

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

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