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 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
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.
- agent/references
- agent/type
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/severity
- agent/author
- agent/last-modified-date
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/atlassian
- canonical/atlassian jira
- version/atlassian jira/3.12