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

> Krusader stores passwords in cleartext in configuration files, allowing local attackers to read sensitive credentials.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Nov 2005
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2005-3856, GHSA-p78f-ff59-jj59

## What is CVE-2005-3856?

CVE-2005-3856 is a medium-severity vulnerability in n/a, published on 27 Nov 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Popular URL capability (popularurls.cpp) in Krusader 1.60.0 and 1.70.0-beta1 saves passwords in cleartext in the krusaderrc file when the user enters URLs containing passwords in the panel URL field, which might allow attackers to access other sites.

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

It affects 1 product.


Products: Krusader Krusader.

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

Upgrade to a fixed version.

## Is CVE-2005-3856 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-3816](https://insights.sbomify.com/CVE-2006-3816/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-3856 is a medium-severity vulnerability in n/a, published on 27 Nov 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-3856 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-3856/ (Markdown: https://insights.sbomify.com/CVE-2005-3856/index.md)
```

## Sources

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

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