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

> Remote attackers can hijack or disrupt TCP sessions by flooding packets with guessed initial sequence numbers due to weak randomization.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 24 May 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jvrp-wcjq-4xx5

## What is CVE-2001-0328?

CVE-2001-0328 is a medium-severity vulnerability in n/a, published on 24 May 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TCP implementations that use random increments for initial sequence numbers (ISN) can allow remote attackers to perform session hijacking or disruption by injecting a flood of packets with a range of ISN values, one of which may match the expected ISN.

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


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

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

## Is CVE-2001-0328 being exploited?

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

Public exploit code:

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

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0328 is a medium-severity vulnerability in n/a, published on 24 May 2001. 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-0328 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-0328/ (Markdown: https://insights.sbomify.com/CVE-2001-0328/index.md)
```

## Sources

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

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