# CVE-2002-1849: Denial of service in n/a

> Remote attackers can cause denial of service in ParaChat Server by exploiting session handling flaws to fill chat rooms with invalid users.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jun 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-jq4q-qcfh-gq3c

## What is CVE-2002-1849?

CVE-2002-1849 is a medium-severity denial of service vulnerability in n/a, published on 28 Jun 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

ParaChat Server 4.0 does not log users off if the browser's back button is used, which allows remote attackers to cause a denial of service by repeatedly logging into a chat room, hitting the back button, then logging into the same chat room as a different user, which fills the chat room with invalid users.

## Which versions are affected by CVE-2002-1849?

It affects 1 product.


Products: Parachat Parachat Server.

## How do I fix CVE-2002-1849?

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

## Is CVE-2002-1849 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1568](https://insights.sbomify.com/CVE-2004-1568/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1849 and fix it if it is affected.

What it is: CVE-2002-1849 is a medium-severity denial of service vulnerability in n/a, published on 28 Jun 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-1849 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-2002-1849/ (Markdown: https://insights.sbomify.com/CVE-2002-1849/index.md)
```

## Sources

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

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