# CVE-2005-0467: Integer overflow in n/a

> Remote attackers can execute arbitrary code on PuTTY clients via malicious SFTP responses exploiting integer overflows, requiring user interaction.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 21 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0467, GHSA-cmv8-452f-24ph

## What is CVE-2005-0467?

CVE-2005-0467 is a high-severity vulnerability in n/a, published on 21 Feb 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

Multiple integer overflows in the (1) sftp_pkt_getstring and (2) fxp_readdir_recv functions in the PSFTP and PSCP clients for PuTTY 0.56, and possibly earlier versions, allow remote malicious web sites to execute arbitrary code via SFTP responses that corrupt the heap after insufficient memory has been allocated.

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

It affects 1 product.


Products: Putty Putty.

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

Upgrade to a fixed version.

## Is CVE-2005-0467 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1008](https://insights.sbomify.com/CVE-2004-1008/): Integer overflow in n/a (critical 10.0)
- [CVE-2019-17067](https://insights.sbomify.com/CVE-2019-17067/): Other in n/a (critical 9.8)
- [CVE-2021-36367](https://insights.sbomify.com/CVE-2021-36367/): Auth bypass in n/a (high 8.1)
- [CVE-2016-6167](https://insights.sbomify.com/CVE-2016-6167/): Other in n/a (high 7.8)
- [CVE-2021-33500](https://insights.sbomify.com/CVE-2021-33500/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0467 is a high-severity vulnerability in n/a, published on 21 Feb 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: There is no known exploitation of CVE-2005-0467 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-2005-0467/ (Markdown: https://insights.sbomify.com/CVE-2005-0467/index.md)
```

## Sources

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

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