# CVE-2007-3718: Other in n/a

> Unspecified vulnerabilities in Apple Safari's SVG parser allow remote attacks with unknown impact, requiring attention from Safari users.

- **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:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 12 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2fhj-34vp-w6xg

## What is CVE-2007-3718?

CVE-2007-3718 is a high-severity vulnerability in Apple Safari, published on 12 Jul 2007. It can be exploited over the network.

### Official description

Multiple unspecified vulnerabilities in the SVG parsing engine in Apple Safari 3 Beta for Windows have unspecified remote attack vectors and impact.  NOTE: this issue contains no actionable information, but it was released by a reliable researcher.

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

It affects 1 product.


Products: Apple Safari.

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

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

## Is CVE-2007-3718 being exploited?

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

## Other vulnerabilities in Apple Safari

- [CVE-2015-5780](https://insights.sbomify.com/CVE-2015-5780/): Security feature bypass in n/a (critical 10.0)
- [CVE-2014-1300](https://insights.sbomify.com/CVE-2014-1300/): Code injection in n/a (critical 10.0)
- [CVE-2014-1303](https://insights.sbomify.com/CVE-2014-1303/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-1120](https://insights.sbomify.com/CVE-2010-1120/): Code injection in n/a (critical 10.0)
- [CVE-2009-0137](https://insights.sbomify.com/CVE-2009-0137/): Cross-site scripting in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3718 is a high-severity vulnerability in Apple Safari, published on 12 Jul 2007. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2007-3718 in the wild and no public exploit code.

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

## Sources

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

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