# CVE-2007-1397: Memory corruption in n/a

> Remote attackers can execute arbitrary code via stack-based buffer overflows in the FiSH encryption library functions.

- **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:** Not needed
- **Fix available:** Yes
- **Published:** 10 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-46qm-vrjp-cc4w, MINI-v72q-78jg-jwm6

## What is CVE-2007-1397?

CVE-2007-1397 is a critical memory corruption vulnerability in n/a, published on 10 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in the (1) ExtractRnick and (2) decrypt_topic_332 functions in FiSH allow remote attackers to execute arbitrary code via long strings.

## Which versions are affected by CVE-2007-1397?

It affects 1 product.


Products: Fish Fish.

## How do I fix CVE-2007-1397?

Upgrade to a fixed version.

## Is CVE-2007-1397 being exploited?

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

Public exploit code:

- FiSH-irssi - Multiple Remote Buffer Overflow Vulnerabilities (exploitdb)
- FiSH-irssi 0.99 - Evil ircd Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1397 and fix it if it is affected.

What it is: CVE-2007-1397 is a critical memory corruption vulnerability in n/a, published on 10 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1397 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-2007-1397/ (Markdown: https://insights.sbomify.com/CVE-2007-1397/index.md)
```

## Sources

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

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