# CVE-2004-2182: Session fixation vulnerability in Macromedia JRun 4.0 allows remote attackers to hijack user sessions by pre-setting the user session ID inf


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Jul 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-gr3m-3w4f-5p6g

## What is CVE-2004-2182?

CVE-2004-2182 is a high-severity vulnerability in n/a, published on 10 Jul 2005. 

### Official description

Session fixation vulnerability in Macromedia JRun 4.0 allows remote attackers to hijack user sessions by pre-setting the user session ID information used by the session server.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2004-2182?

It affects 1 product.


Products: Macromedia Jrun.

## How do I fix CVE-2004-2182?

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

## Is CVE-2004-2182 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0665](https://insights.sbomify.com/CVE-2002-0665/): Auth bypass in n/a (critical 10.0)
- [CVE-2002-0801](https://insights.sbomify.com/CVE-2002-0801/): Memory corruption in n/a (critical 10.0)
- [CVE-2000-1053](https://insights.sbomify.com/CVE-2000-1053/): Cross-site scripting in n/a (critical 10.0)
- [CVE-2005-4472](https://insights.sbomify.com/CVE-2005-4472/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1513](https://insights.sbomify.com/CVE-2001-1513/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2182 and fix it if it is affected.

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

## Sources

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

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