What is the severity of CVE-2007-6619?

CVE-2007-6619 is considered a moderate severity vulnerability due to its potential for unauthorized language changes.

How do I fix CVE-2007-6619?

To fix CVE-2007-6619, upgrade Atlassian JIRA Enterprise Edition to version 3.12.1 or later.

What systems are affected by CVE-2007-6619?

CVE-2007-6619 affects Atlassian JIRA Enterprise Edition versions prior to 3.12.1.

Can CVE-2007-6619 be exploited remotely?

Yes, CVE-2007-6619 can be exploited remotely by attackers without needing authentication.

What impact does CVE-2007-6619 have on my JIRA installation?

The impact of CVE-2007-6619 is that attackers can change the default language setting in JIRA after initial setup.

Vulnerability/
CVE-2007-6619

high

7.5

CWE

264

3/1/2008

7/8/2024

CVE-2007-6619

First published: Thu Jan 03 2008(Updated: )

The Setup Wizard in Atlassian JIRA Enterprise Edition before 3.12.1 does not properly restrict setup attempts after setup is complete, which allows remote attackers to change the default language.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Atlassian JIRA	<=3.12

Remedy

http://confluence.atlassian.com/display/JIRA/JIRA+Security+Advisory+2007-12-24

Remedy

http://secunia.com/advisories/27954

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2007-6619?
CVE-2007-6619 is considered a moderate severity vulnerability due to its potential for unauthorized language changes.
How do I fix CVE-2007-6619?
To fix CVE-2007-6619, upgrade Atlassian JIRA Enterprise Edition to version 3.12.1 or later.
What systems are affected by CVE-2007-6619?
CVE-2007-6619 affects Atlassian JIRA Enterprise Edition versions prior to 3.12.1.
Can CVE-2007-6619 be exploited remotely?
Yes, CVE-2007-6619 can be exploited remotely by attackers without needing authentication.
What impact does CVE-2007-6619 have on my JIRA installation?
The impact of CVE-2007-6619 is that attackers can change the default language setting in JIRA after initial setup.

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

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-2007-6619?
CVE-2007-6619 is considered a moderate severity vulnerability due to its potential for unauthorized language changes.
How do I fix CVE-2007-6619?
To fix CVE-2007-6619, upgrade Atlassian JIRA Enterprise Edition to version 3.12.1 or later.
What systems are affected by CVE-2007-6619?
CVE-2007-6619 affects Atlassian JIRA Enterprise Edition versions prior to 3.12.1.
Can CVE-2007-6619 be exploited remotely?
Yes, CVE-2007-6619 can be exploited remotely by attackers without needing authentication.
What impact does CVE-2007-6619 have on my JIRA installation?
The impact of CVE-2007-6619 is that attackers can change the default language setting in JIRA after initial setup.