# CVE-2008-6393: Integer overflow in n/a

> Remote attackers can cause a crash or execute arbitrary code in PSI Jabber client via a malicious file transfer request exploiting an integer overflow.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** Yes
- **Published:** 3 Mar 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-6393, DSA-1741-1, GHSA-4p4v-f795-xc4p

## What is CVE-2008-6393?

CVE-2008-6393 is a critical vulnerability in n/a, published on 3 Mar 2009. 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

PSI Jabber client before 0.12.1 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a file transfer request with a negative value in a SOCKS5 option, which bypasses a signed integer check and triggers an integer overflow and a heap-based buffer overflow.

Weakness: CWE-189

## Which versions are affected by CVE-2008-6393?

It affects 1 product.


Products: Psi-Im Psi.

## How do I fix CVE-2008-6393?

Upgrade to a fixed version.

## Is CVE-2008-6393 being exploited?

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

Public exploit code:

- Psi Jabber Client (Windows / Linux) - Remote Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6393 and fix it if it is affected.

What it is: CVE-2008-6393 is a critical vulnerability in n/a, published on 3 Mar 2009. 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-2008-6393 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-2008-6393/ (Markdown: https://insights.sbomify.com/CVE-2008-6393/index.md)
```

## Sources

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

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