CVE-2008-6531: Code Injection

Published Mar 26, 2009
·
Updated

The WebWork 1 web application framework in Atlassian JIRA before 3.13.2 allows remote attackers to invoke exposed public JIRA methods via a crafted URL that is dynamically transformed into method calls, aka "WebWork 1 Parameter Injection Hole."

Affected Software

233 affected components
Atlassian Jira<3.13.2
Atlassian Jira=3.2.2
Atlassian Jira=3.2.2
Atlassian Jira=2.6.1
Atlassian Jira=3.9
Atlassian Jira=2.4.1
Atlassian Jira=3.0.3
Atlassian Jira=2.3
Atlassian Jira=3.13
Atlassian Jira=3.2.2
Atlassian Jira=3.10.1
Atlassian Jira=3.0.2
Atlassian Jira=3.6
Atlassian Jira=3.7.2
Atlassian Jira=3.3
Atlassian Jira=3.0.1
Atlassian Jira=2.2.1
Atlassian Jira=3.6.5
Atlassian Jira=3.7.3
Atlassian Jira=3.5.3
Atlassian Jira=3.6.2
Atlassian Jira=2.3
Atlassian Jira=3.10
Atlassian Jira=3.0
Atlassian Jira=3.9
Atlassian Jira=3.6.4
Atlassian Jira=3.12.3
Atlassian Jira=3.12.2
Atlassian Jira=3.5.3
Atlassian Jira=3.4.3
Atlassian Jira=3.12
Atlassian Jira=3.4.1
Atlassian Jira=3.12
Atlassian Jira=3.3.2
Atlassian Jira=3.4.1
Atlassian Jira=3.5.2
Atlassian Jira=3.8.1
Atlassian Jira=3.8.1
Atlassian Jira=3.6.1
Atlassian Jira=3.3.3
Atlassian Jira=3.7
Atlassian Jira=3.6.4
Atlassian Jira=3.7.1
Atlassian Jira=2.5.2
Atlassian Jira=3.6.4
Atlassian Jira=3.12.1
Atlassian Jira=3.1
Atlassian Jira=3.8
Atlassian Jira=3.6
Atlassian Jira=3.9.3
Atlassian Jira=2.2.1
Atlassian Jira=3.6.5
Atlassian Jira=3.6.2
Atlassian Jira=3.6.2
Atlassian Jira=3.9.2
Atlassian Jira=3.6
Atlassian Jira=3.9.2
Atlassian Jira=3.3.3
Atlassian Jira=2.2
Atlassian Jira=3.10
Atlassian Jira=3.1
Atlassian Jira=3.11
Atlassian Jira=3.0.2
Atlassian Jira=3.9.3
Atlassian Jira=2.4.1
Atlassian Jira=3.9.3
Atlassian Jira=3.4.3
Atlassian Jira=3.10
Atlassian Jira=3.5.3
Atlassian Jira=3.6.1
Atlassian Jira=3.1
Atlassian Jira=3.12.1
Atlassian Jira=3.2
Atlassian Jira=3.12.3
Atlassian Jira=3.2
Atlassian Jira=3.3.1
Atlassian Jira=3.6.2
Atlassian Jira=3.12.3
Atlassian Jira=2.5.3
Atlassian Jira=3.1
Atlassian Jira=3.11
Atlassian Jira=3.1.1
Atlassian Jira=3.2.3
Atlassian Jira=2.5.2
Atlassian Jira=3.10.1
Atlassian Jira=3.9
Atlassian Jira=3.4.2
Atlassian Jira=3.7
Atlassian Jira=3.13.1
Atlassian Jira=3.5.1
Atlassian Jira=3.0
Atlassian Jira=3.5.2
Atlassian Jira=3.4.2
Atlassian Jira=3.3.1
Atlassian Jira=3.7
Atlassian Jira=3.12.3
Atlassian Jira=3.7.4
Atlassian Jira=2.5.1
Atlassian Jira=3.9.3
Atlassian Jira=3.13
Atlassian Jira=3.5.1
Atlassian Jira=3.5
Atlassian Jira=3.0.1
Atlassian Jira=3.3.2
Atlassian Jira=3.7.4
Atlassian Jira=3.8
Atlassian Jira=2.5.1
Atlassian Jira=3.7.2
Atlassian Jira=3.2.1
Atlassian Jira=3.0
Atlassian Jira=3.2.1
Atlassian Jira=2.1
Atlassian Jira=3.5.1
Atlassian Jira=3.6.5
Atlassian Jira=3.6.3
Atlassian Jira=3.13.1
Atlassian Jira=3.13.1
Atlassian Jira=3.3.3
Atlassian Jira=3.2.3
Atlassian Jira=3.1.1
Atlassian Jira=3.1.1
Atlassian Jira=2.6
Atlassian Jira=3.13
Atlassian Jira=3.8.1
Atlassian Jira=2.2
Atlassian Jira=3.6.4
Atlassian Jira=2.6
Atlassian Jira=3.10.2
Atlassian Jira=3.10.2
Atlassian Jira=3.2.1
Atlassian Jira=3.2
Atlassian Jira=3.3
Atlassian Jira=2.1
Atlassian Jira=2.5.1
Atlassian Jira=3.1.1
Atlassian Jira<=3.13.1
Atlassian Jira=3.4.1
Atlassian Jira=3.3.1
Atlassian Jira=3.6.1
Atlassian Jira=3.12.2
Atlassian Jira=3.0.3
Atlassian Jira=2.3
Atlassian Jira=3.9
Atlassian Jira=3.7.1
Atlassian Jira=2.4.1
Atlassian Jira=3.8
Atlassian Jira=3.12.2
Atlassian Jira=3.3
Atlassian Jira=3.10.1
Atlassian Jira=3.7.4
Atlassian Jira=3.2
Atlassian Jira=3.7.2
Atlassian Jira=3.2.3
Atlassian Jira=3.9.1
Atlassian Jira=3.10.2
Atlassian Jira=3.7.1
Atlassian Jira=3.0.2
Atlassian Jira=3.9.1
Atlassian Jira=2.5.2
Atlassian Jira=3.5.2
Atlassian Jira=3.8
Atlassian Jira=3.6.1
Atlassian Jira=3.9.1
Atlassian Jira=3.5.1
Atlassian Jira=3.3
Atlassian Jira=3.0.3
Atlassian Jira=3.9.2
Atlassian Jira=2.1
Atlassian Jira=3.4.2
Atlassian Jira=2.6
Atlassian Jira=3.10.1
Atlassian Jira=2.2
Atlassian Jira=3.12
Atlassian Jira=2.5.3
Atlassian Jira=2.6.1
Atlassian Jira=3.7.3
Atlassian Jira=2.2
Atlassian Jira=3.5
Atlassian Jira=3.9.2
Atlassian Jira=3.6.5
Atlassian Jira=3.5
Atlassian Jira=3.3.3
Atlassian Jira=2.6.1
Atlassian Jira=3.3.2
Atlassian Jira=2.6.1
Atlassian Jira=2.6
Atlassian Jira=3.8.1
Atlassian Jira=3.0.3
Atlassian Jira=3.4.2
Atlassian Jira=3.7.3
Atlassian Jira=2.2.1
Atlassian Jira=3.0
Atlassian Jira=3.11
Atlassian Jira=3.9.1
Atlassian Jira=3.7
Atlassian Jira=2.5.3
Atlassian Jira=3.5.3
Atlassian Jira=2.4.1
Atlassian Jira=3.12.1
Atlassian Jira=3.7.2
Atlassian Jira=3.2.3
Atlassian Jira=2.1
Atlassian Jira=3.5
Atlassian Jira=3.11
Atlassian Jira=3.6.3
Atlassian Jira=2.5.3
Atlassian Jira=3.6
Atlassian Jira=3.12.1
Atlassian Jira=3.3.1
Atlassian Jira=3.4.3
Atlassian Jira=3.7.3
Atlassian Jira=3.3.2
Atlassian Jira=3.6.3
Atlassian Jira=3.0.2
Atlassian Jira=2.3
Atlassian Jira=3.12
Atlassian Jira=3.0.1
Atlassian Jira=3.7.4
Atlassian Jira=3.4.1
Atlassian Jira=3.13
Atlassian Jira=3.2.2
Atlassian Jira=3.5.2
Atlassian Jira=2.5.2
Atlassian Jira=3.6.3
Atlassian Jira=2.5.1
Atlassian Jira=3.10
Atlassian Jira=3.2.1
Atlassian Jira=3.4.3
Atlassian Jira=3.7.1
Atlassian Jira=3.0.1
Atlassian Jira=3.12.2
Atlassian Jira=3.10.2
Atlassian Jira=2.2.1

Remediation

Patch Available

http://confluence.atlassian.com/display/JIRA/JIRA+Security+Advisory+2008-12-09

Event History

Mar 26, 2009
CVE Published
via MITRE·08:28 PM
Data Sourced
via MITRE·08:28 PM
Description
Data Sourced
via NVD·09:00 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2008-6531?

CVE-2008-6531 is considered a critical vulnerability due to its capability to allow remote code execution.

2

How do I fix CVE-2008-6531?

To fix CVE-2008-6531, upgrade Atlassian JIRA to version 3.13.2 or later.

3

What software versions are affected by CVE-2008-6531?

CVE-2008-6531 affects Atlassian JIRA versions before 3.13.2, including versions such as 3.2.2, 3.9, and 2.6.1.

4

What type of attack can exploit CVE-2008-6531?

CVE-2008-6531 can be exploited through parameter injection via crafted URLs, allowing attackers to invoke JIRA methods.

5

Is there a workaround for CVE-2008-6531 if I can't upgrade?

There is no official workaround for CVE-2008-6531; upgrading to the latest version is the recommended action.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203