# CVE-2009-1560: Information disclosure in n/a

> Remote attackers can read HTML source code to obtain cleartext passwords and wireless keys from the Cisco Linksys WVC54GCA camera.

- **Severity:** High 7.8 (`AV:N/AC:L/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:** Not needed
- **Fix available:** No
- **Published:** 6 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q8v9-gg98-chwq

## What is CVE-2009-1560?

CVE-2009-1560 is a high-severity vulnerability in n/a, published on 6 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Cisco Linksys WVC54GCA wireless video camera with firmware 1.00R22 and 1.00R24 stores passwords and wireless-network keys in cleartext in (1) pass_wd.htm and (2) Wsecurity.htm, which allows remote attackers to obtain sensitive information by reading the HTML source code.

Weakness: CWE-310

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

It affects 1 product.


Products: Cisco Wvc54gc.

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

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

## Is CVE-2009-1560 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-4391](https://insights.sbomify.com/CVE-2008-4391/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1560 is a high-severity vulnerability in n/a, published on 6 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-1560 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-1560/ (Markdown: https://insights.sbomify.com/CVE-2009-1560/index.md)
```

## Sources

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

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