# CVE-2004-2530: Other in n/a

> Remote attackers can spoof file extensions in Gadu-Gadu by using long filenames with spaces, potentially tricking users into executing malicious files.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/I:P/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:** 25 Oct 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-ghgp-g378-8742

## What is CVE-2004-2530?

CVE-2004-2530 is a low-severity vulnerability in n/a, published on 25 Oct 2005. 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

Visual truncation vulnerability in Gadu-Gadu allows remote attackers to spoof the file extension on transmitted files via a filename with a large number of spaces followed by the real extension, which is not displayed in the dialog box.

## Which versions are affected by CVE-2004-2530?


## How do I fix CVE-2004-2530?

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

## Is CVE-2004-2530 being exploited?

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

Public exploit code:

- Gadu-Gadu 6.0 - File Download Filename Obfuscation (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2530 and fix it if it is affected.

What it is: CVE-2004-2530 is a low-severity vulnerability in n/a, published on 25 Oct 2005. An attacker can exploit it over the internet without logging in, 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-2004-2530 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-2004-2530/ (Markdown: https://insights.sbomify.com/CVE-2004-2530/index.md)
```

## Sources

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

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