# CVE-2005-1686: Other in n/a

> Attackers can crash gedit via format string specifiers in filenames, potentially triggered by browsers or email clients.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 May 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-1686, DSA-753-1, GHSA-r7hv-4wrp-wf62, RHSA-2005:499

## What is CVE-2005-1686?

CVE-2005-1686 is a low-severity vulnerability in n/a, published on 25 May 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Format string vulnerability in gedit 2.10.2 may allow attackers to cause a denial of service (application crash) via a bin file with format string specifiers in the filename.  NOTE: while this issue is triggered on the command line by the gedit user, it has been reported that web browsers and email clients could be configured to provide a file name as an argument to gedit, so there is a valid attack that crosses security boundaries.

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gedit` | Red Hat:enterprise_linux:3::as | All versions | 1:2.2.2-4.rhel3 |
| `gedit-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 1:2.2.2-4.rhel3 |
| `gedit` | Red Hat:enterprise_linux:3::desktop | All versions | 1:2.2.2-4.rhel3 |
| `gedit-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 1:2.2.2-4.rhel3 |
| `gedit` | Red Hat:enterprise_linux:3::es | All versions | 1:2.2.2-4.rhel3 |
| `gedit-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 1:2.2.2-4.rhel3 |
| `gedit` | Red Hat:enterprise_linux:3::ws | All versions | 1:2.2.2-4.rhel3 |
| `gedit-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 1:2.2.2-4.rhel3 |
| `gedit` | Red Hat:enterprise_linux:4::as | All versions | 1:2.8.1-4 |
| `gedit-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 1:2.8.1-4 |
| `gedit-devel` | Red Hat:enterprise_linux:4::as | All versions | 1:2.8.1-4 |
| `gedit` | Red Hat:enterprise_linux:4::desktop | All versions | 1:2.8.1-4 |
| `gedit-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 1:2.8.1-4 |
| `gedit-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 1:2.8.1-4 |
| `gedit` | Red Hat:enterprise_linux:4::es | All versions | 1:2.8.1-4 |
| `gedit-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 1:2.8.1-4 |
| `gedit-devel` | Red Hat:enterprise_linux:4::es | All versions | 1:2.8.1-4 |
| `gedit` | Red Hat:enterprise_linux:4::ws | All versions | 1:2.8.1-4 |
| `gedit-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 1:2.8.1-4 |
| `gedit-devel` | Red Hat:enterprise_linux:4::ws | All versions | 1:2.8.1-4 |

Products: Gnome Gedit.

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

Apply the vendor's patch.

## Is CVE-2005-1686 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1686 exists.

Public exploit code:

- Gedit 2.x - Filename Format String (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-14108](https://insights.sbomify.com/CVE-2017-14108/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-1686 is a low-severity vulnerability in n/a, published on 25 May 2005. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-1686 exists.

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-1686/ (Markdown: https://insights.sbomify.com/CVE-2005-1686/index.md)
```

## Sources

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

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