# CVE-2005-2462: Information disclosure in n/a

> Kayako liveResponse logs passwords in plaintext URLs, allowing attackers to steal credentials and gain unauthorized access.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/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:** 6 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-965c-8xf8-5hcf

## What is CVE-2005-2462?

CVE-2005-2462 is a low-severity vulnerability in n/a, published on 6 Jun 2006. 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

Kayako liveResponse 2.x, when logging in a user, records the password in plaintext in the URL, which allows local users and possibly remote attackers to gain privileges.

## Which versions are affected by CVE-2005-2462?

It affects 1 product.


Products: Kayako Liveresponse.

## How do I fix CVE-2005-2462?

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

## Is CVE-2005-2462 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-2461](https://insights.sbomify.com/CVE-2005-2461/): SQL injection in n/a (medium 6.4)
- [CVE-2005-2463](https://insights.sbomify.com/CVE-2005-2463/): Information disclosure in n/a (medium 6.4)
- [CVE-2005-2460](https://insights.sbomify.com/CVE-2005-2460/): Cross-site scripting in n/a (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2462 and fix it if it is affected.

What it is: CVE-2005-2462 is a low-severity vulnerability in n/a, published on 6 Jun 2006. 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-2005-2462 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-2005-2462/ (Markdown: https://insights.sbomify.com/CVE-2005-2462/index.md)
```

## Sources

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

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