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

> Remote attackers can execute arbitrary code by tricking users into opening a malicious SMIL file with a long wallclock value in RealPlayer.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** Yes
- **Published:** 26 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7hxv-5pvm-4mww, RHSA-2007:0605

## What is CVE-2007-3410?

CVE-2007-3410 is a critical memory corruption vulnerability in Realnetworks Realplayer, published on 26 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

Stack-based buffer overflow in the SmilTimeValue::parseWallClockValue function in smlprstime.cpp in RealNetworks RealPlayer 10, 10.1, and possibly 10.5, RealOne Player, RealPlayer Enterprise, and Helix Player 10.5-GOLD and 10.0.5 through 10.0.8, allows remote attackers to execute arbitrary code via an SMIL (SMIL2) file with a long wallclock value.

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

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

It affects 4 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `HelixPlayer` | Red Hat:enterprise_linux:4::as | All versions | 1:1.0.6-0.EL4.2 |
| `HelixPlayer-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 1:1.0.6-0.EL4.2 |
| `HelixPlayer` | Red Hat:enterprise_linux:4::desktop | All versions | 1:1.0.6-0.EL4.2 |
| `HelixPlayer-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 1:1.0.6-0.EL4.2 |
| `HelixPlayer` | Red Hat:enterprise_linux:4::es | All versions | 1:1.0.6-0.EL4.2 |
| `HelixPlayer-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 1:1.0.6-0.EL4.2 |
| `HelixPlayer` | Red Hat:enterprise_linux:4::ws | All versions | 1:1.0.6-0.EL4.2 |
| `HelixPlayer-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 1:1.0.6-0.EL4.2 |

Products: Realnetworks Helix Player, Realnetworks Realone Player, Realnetworks Realplayer, Realnetworks Realplayer Enterprise.

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

Apply the vendor's patch.

## Is CVE-2007-3410 being exploited?

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

Public exploit code:

- RealNetworks RealPlayer/HelixPlayer - SMIL wallclock Stack Overflow (PoC) (exploitdb)

## Other vulnerabilities in Realnetworks Realplayer

- [CVE-2009-4241](https://insights.sbomify.com/CVE-2009-4241/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-4242](https://insights.sbomify.com/CVE-2009-4242/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-4243](https://insights.sbomify.com/CVE-2009-4243/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-4244](https://insights.sbomify.com/CVE-2009-4244/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-4245](https://insights.sbomify.com/CVE-2009-4245/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3410 is a critical memory corruption vulnerability in Realnetworks Realplayer, published on 26 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-3410 exists.

Affected product: Realnetworks Realplayer. 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-3410/ (Markdown: https://insights.sbomify.com/CVE-2007-3410/index.md)
```

## Sources

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

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