# CVE-2008-0729: Denial of service in n/a

> Remote attackers can crash Mobile Safari on iPhones by sending malicious JavaScript that exhausts memory, requiring user interaction to visit a crafted page.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/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:** 12 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6vr8-qvq2-r64x

## What is CVE-2008-0729?

CVE-2008-0729 is a high-severity denial of service vulnerability in n/a, published on 12 Feb 2008. 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

Mobile Safari on Apple iPhone 1.1.2 and 1.1.3 allows remote attackers to cause a denial of service (memory exhaustion and device crash) via certain JavaScript code that constructs a long string and an array containing long string elements, possibly a related issue to CVE-2006-3677.  NOTE: some of these details are obtained from third party information.

Weakness: CWE-399

## Which versions are affected by CVE-2008-0729?

It affects 1 product.


Products: Apple Mobile Safari.

## How do I fix CVE-2008-0729?

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

## Is CVE-2008-0729 being exploited?

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

Public exploit code:

- Apple iOS Mobile Safari - Memory Exhaustion Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0729 and fix it if it is affected.

What it is: CVE-2008-0729 is a high-severity denial of service vulnerability in n/a, published on 12 Feb 2008. 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-2008-0729 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-2008-0729/ (Markdown: https://insights.sbomify.com/CVE-2008-0729/index.md)
```

## Sources

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

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