# CVE-2007-1767: Denial of service in n/a

> Remote attackers can crash the AOL browser via unspecified vectors in Deskbar.dll and Toolbar.dll, requiring user interaction.

- **Severity:** High 7.8 (`AV:N/AC:L/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:** 30 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r674-9g5f-h5vc

## What is CVE-2007-1767?

CVE-2007-1767 is a high-severity denial of service vulnerability in n/a, published on 30 Mar 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

Unspecified vulnerability in (1) Deskbar.dll and (2) Toolbar.dll in AOL 9.0 before February 2007 allows remote attackers to cause a denial of service (browser crash) via unknown vectors.

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

It affects 1 product.


Products: Aol Aol Client Software.

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

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

## Is CVE-2007-1767 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-0316](https://insights.sbomify.com/CVE-2006-0316/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-6442](https://insights.sbomify.com/CVE-2006-6442/): Memory corruption in n/a (critical 9.3)
- [CVE-2006-0526](https://insights.sbomify.com/CVE-2006-0526/): Privilege escalation in n/a (high 7.2)
- [CVE-2005-2597](https://insights.sbomify.com/CVE-2005-2597/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1767 is a high-severity denial of service vulnerability in n/a, published on 30 Mar 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: There is no known exploitation of CVE-2007-1767 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-1767/ (Markdown: https://insights.sbomify.com/CVE-2007-1767/index.md)
```

## Sources

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

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