# CVE-2020-12755: Information disclosure in n/a

> KDE kio-extras may unintentionally store passwords in KWallet even when the user has not enabled password keeping, leading to potential credential exposure.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-12755, GHSA-6qhj-5898-8677, MGASA-2020-0371, UBUNTU-CVE-2020-12755

## What is CVE-2020-12755?

CVE-2020-12755 is a low-severity vulnerability in n/a, published on 9 May 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

fishProtocol::establishConnection in fish/fish.cpp in KDE kio-extras through 20.04.0 makes a cacheAuthentication call even if the user had not set the keepPassword option. This may lead to unintended KWallet storage of a password.

## Which versions are affected by CVE-2020-12755?

It affects 1 product.


Products: Kde Kio-Extras.

## How do I fix CVE-2020-12755?

Apply the vendor's patch.

## Is CVE-2020-12755 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-12755 and fix it if it is affected.

What it is: CVE-2020-12755 is a low-severity vulnerability in n/a, published on 9 May 2020. 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-2020-12755 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-2020-12755/ (Markdown: https://insights.sbomify.com/CVE-2020-12755/index.md)
```

## Sources

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

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