# CVE-2008-7190: Cross-site scripting in n/a

> An unspecified vulnerability in Adium involving javascript: URLs may allow cross-site scripting attacks, requiring user interaction.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Sep 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-86mv-83jj-46wg

## What is CVE-2008-7190?

CVE-2008-7190 is a critical cross-site scripting vulnerability in n/a, published on 9 Sep 2009. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Unspecified vulnerability in Adium before 1.2 has unknown impact and attack vectors related to javascript: URLs, possibly cross-site scripting (XSS).

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

It affects 1 product.


Products: Adium Adium.

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

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

## Is CVE-2008-7190 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2694](https://insights.sbomify.com/CVE-2009-2694/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-0013](https://insights.sbomify.com/CVE-2010-0013/): Path traversal in n/a (high 7.5)
- [CVE-2008-2927](https://insights.sbomify.com/CVE-2008-2927/): Integer overflow in n/a (medium 6.8)
- [CVE-2010-0277](https://insights.sbomify.com/CVE-2010-0277/): Memory corruption in n/a (medium 5.0)
- [CVE-2009-3615](https://insights.sbomify.com/CVE-2009-3615/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-7190 is a critical cross-site scripting vulnerability in n/a, published on 9 Sep 2009. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-7190 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-2008-7190/ (Markdown: https://insights.sbomify.com/CVE-2008-7190/index.md)
```

## Sources

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

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