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

> Local users or remote attackers can obtain sensitive information because Kate and Kwrite fail to preserve original file permissions on backup files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** Yes
- **Published:** 26 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-804-2, GHSA-2p38-wq56-wg8h, RHSA-2005:612

## What is CVE-2005-1920?

CVE-2005-1920 is a high-severity vulnerability in Debian Debian Linux, published on 26 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The (1) Kate and (2) Kwrite applications in KDE KDE 3.2.x through 3.4.0 do not properly set the same permissions on the backup file as were set on the original file, which could allow local users and possibly remote attackers to obtain sensitive information.

Weakness: CWE-281 (Improper Preservation of Permissions)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kdelibs` | Red Hat:enterprise_linux:4::as | All versions | 6:3.3.1-3.11 |
| `kdelibs-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 6:3.3.1-3.11 |
| `kdelibs-devel` | Red Hat:enterprise_linux:4::as | All versions | 6:3.3.1-3.11 |
| `kdelibs` | Red Hat:enterprise_linux:4::desktop | All versions | 6:3.3.1-3.11 |
| `kdelibs-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 6:3.3.1-3.11 |
| `kdelibs-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 6:3.3.1-3.11 |
| `kdelibs` | Red Hat:enterprise_linux:4::es | All versions | 6:3.3.1-3.11 |
| `kdelibs-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 6:3.3.1-3.11 |
| `kdelibs-devel` | Red Hat:enterprise_linux:4::es | All versions | 6:3.3.1-3.11 |
| `kdelibs` | Red Hat:enterprise_linux:4::ws | All versions | 6:3.3.1-3.11 |
| `kdelibs-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 6:3.3.1-3.11 |
| `kdelibs-devel` | Red Hat:enterprise_linux:4::ws | All versions | 6:3.3.1-3.11 |

Products: Debian Debian Linux, Kde Kde.

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

Apply the vendor's patch.

## Is CVE-2005-1920 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1920 is a high-severity vulnerability in Debian Debian Linux, published on 26 Jul 2005. 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-2005-1920 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-1920/ (Markdown: https://insights.sbomify.com/CVE-2005-1920/index.md)
```

## Sources

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

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