# CVE-2009-5097: Cross-site scripting in n/a

> Remote attackers can execute arbitrary JavaScript in Palm Pre WebOS email clients, potentially reading local databases, requiring user interaction to view the malicious email.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:C/I:N/A:N`)
- **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:** 13 Sep 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-6m4w-j5fc-2m7r

## What is CVE-2009-5097?

CVE-2009-5097 is a high-severity cross-site scripting vulnerability in n/a, published on 13 Sep 2011. 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

Palm Pre WebOS 1.1 and earlier processes JavaScript in email messages, which allows remote attackers to execute arbitrary JavaScript, as demonstrated by reading PalmDatabase.db3.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2009-5097?

It affects 1 product.


Products: Hp Palm Pre Webos.

## How do I fix CVE-2009-5097?

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

## Is CVE-2009-5097 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-5071](https://insights.sbomify.com/CVE-2009-5071/): Other in n/a (critical 10.0)
- [CVE-2009-5098](https://insights.sbomify.com/CVE-2009-5098/): Denial of service in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5097 and fix it if it is affected.

What it is: CVE-2009-5097 is a high-severity cross-site scripting vulnerability in n/a, published on 13 Sep 2011. 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-2009-5097 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-2009-5097/ (Markdown: https://insights.sbomify.com/CVE-2009-5097/index.md)
```

## Sources

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

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