What is the severity of CVE-2008-6832?

CVE-2008-6832 is classified as a moderate severity vulnerability due to its potential for authentication hijacking.

How do I fix CVE-2008-6832?

To fix CVE-2008-6832, it is recommended to upgrade Atlassian JIRA Enterprise Edition to a version that does not contain this vulnerability.

Which versions of Atlassian JIRA are affected by CVE-2008-6832?

CVE-2008-6832 specifically affects Atlassian JIRA Enterprise Edition version 3.13.

What type of vulnerability is CVE-2008-6832?

CVE-2008-6832 is a cross-site request forgery (CSRF) vulnerability.

What can attackers achieve with CVE-2008-6832?

Attackers exploiting CVE-2008-6832 can hijack the authentication of users through unspecified vectors.

Vulnerability/
CVE-2008-6832

medium

6.8

CWE

352

8/6/2009

7/8/2024

CVE-2008-6832: CSRF

First published: Mon Jun 08 2009(Updated: )

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.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Atlassian JIRA	=3.13

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2008-6832?
CVE-2008-6832 is classified as a moderate severity vulnerability due to its potential for authentication hijacking.
How do I fix CVE-2008-6832?
To fix CVE-2008-6832, it is recommended to upgrade Atlassian JIRA Enterprise Edition to a version that does not contain this vulnerability.
Which versions of Atlassian JIRA are affected by CVE-2008-6832?
CVE-2008-6832 specifically affects Atlassian JIRA Enterprise Edition version 3.13.
What type of vulnerability is CVE-2008-6832?
CVE-2008-6832 is a cross-site request forgery (CSRF) vulnerability.
What can attackers achieve with CVE-2008-6832?
Attackers exploiting CVE-2008-6832 can hijack the authentication of users through unspecified vectors.

collector/nvd-historical
collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/author
agent/last-modified-date
agent/weakness
agent/tags
agent/event
agent/description
agent/first-publish-date
agent/source
vendor/atlassian
canonical/atlassian jira
version/atlassian jira/3.13

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2008-6832?
CVE-2008-6832 is classified as a moderate severity vulnerability due to its potential for authentication hijacking.
How do I fix CVE-2008-6832?
To fix CVE-2008-6832, it is recommended to upgrade Atlassian JIRA Enterprise Edition to a version that does not contain this vulnerability.
Which versions of Atlassian JIRA are affected by CVE-2008-6832?
CVE-2008-6832 specifically affects Atlassian JIRA Enterprise Edition version 3.13.
What type of vulnerability is CVE-2008-6832?
CVE-2008-6832 is a cross-site request forgery (CSRF) vulnerability.
What can attackers achieve with CVE-2008-6832?
Attackers exploiting CVE-2008-6832 can hijack the authentication of users through unspecified vectors.