CVE-2007-6618
First published: Thu Jan 03 2008(Updated: )
JIRA Enterprise Edition before 3.12.1 allows remote attackers to delete another user's shared filter via a modified filter ID.
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-6618?
CVE-2007-6618 is classified as a medium-severity vulnerability due to its potential impact on user data.
How do I fix CVE-2007-6618?
To fix CVE-2007-6618, upgrade to Atlassian JIRA Enterprise Edition version 3.12.1 or later.
What versions of JIRA are affected by CVE-2007-6618?
CVE-2007-6618 affects Atlassian JIRA Enterprise Edition versions prior to 3.12.1.
What kind of attack does CVE-2007-6618 enable?
CVE-2007-6618 enables remote attackers to delete another user's shared filters.
Is there a workaround for CVE-2007-6618?
There is no documented workaround for CVE-2007-6618, so upgrading is the recommended action.
- collector/nvd-historical
- collector/nvd-index
- agent/references
- agent/softwarecombine
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/remedy
- 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