# CVE-2008-6832: Cross-site request forgery in n/a

> Remote attackers can hijack user authentication in JIRA Enterprise Edition via cross-site request forgery, requiring victim interaction.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 8 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-77v5-v9v5-mwpv

## What is CVE-2008-6832?

CVE-2008-6832 is a medium-severity vulnerability in Atlassian Jira, published on 8 Jun 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in Atlassian JIRA Enterprise Edition 3.13 allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.  NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2008-6832?

It affects 1 product.


Products: Atlassian Jira.

## How do I fix CVE-2008-6832?

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

## Is CVE-2008-6832 being exploited?

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

## Other vulnerabilities in Atlassian Jira

- [CVE-2020-14172](https://insights.sbomify.com/CVE-2020-14172/): Deserialization in Jira Server (critical 9.8)
- [CVE-2019-20409](https://insights.sbomify.com/CVE-2019-20409/): Code injection in Jira Server (critical 9.8)
- [CVE-2017-5983](https://insights.sbomify.com/CVE-2017-5983/): Deserialization in n/a (critical 9.8)
- [CVE-2010-1165](https://insights.sbomify.com/CVE-2010-1165/): Code injection in n/a (critical 9.0)
- [CVE-2016-4319](https://insights.sbomify.com/CVE-2016-4319/): Cross-site request forgery in Atlassian JIRA Server before 7.1.9 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6832 and fix it if it is affected.

What it is: CVE-2008-6832 is a medium-severity vulnerability in Atlassian Jira, published on 8 Jun 2009. 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-2008-6832 in the wild and no public exploit code.

Affected product: Atlassian Jira. 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-2008-6832/ (Markdown: https://insights.sbomify.com/CVE-2008-6832/index.md)
```

## Sources

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

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