# CVE-2001-1104: Other in n/a

> Remote attackers can spoof or hijack sessions due to predictable TCP sequence numbers in SonicWALL SOHO devices.

- **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:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-36gm-vqvg-q7qc

## What is CVE-2001-1104?

CVE-2001-1104 is a high-severity vulnerability in n/a, published on 15 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SonicWALL SOHO uses easily predictable TCP sequence numbers, which allows remote attackers to spoof or hijack sessions.

## Which versions are affected by CVE-2001-1104?

It affects 1 product.


Products: Sonicwall Soho Firmware.

## How do I fix CVE-2001-1104?

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

## Is CVE-2001-1104 being exploited?

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

Public exploit code:

- Linux Kernel 2.2 - Predictable TCP Initial Sequence Number (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-1006](https://insights.sbomify.com/CVE-2005-1006/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1104 and fix it if it is affected.

What it is: CVE-2001-1104 is a high-severity vulnerability in n/a, published on 15 Mar 2002. 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-2001-1104 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-2001-1104/ (Markdown: https://insights.sbomify.com/CVE-2001-1104/index.md)
```

## Sources

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

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