CVE-2008-5646: High severity Trac Trac vulnerability
Published Dec 17, 2008
·Updated
Unspecified vulnerability in Trac before 0.11.2 allows attackers to cause a denial of service via unknown attack vectors related to "certain wiki markup."
Affected Software
33 affected componentsFixes available
pip/Trac<0.11.2
0.11.2
Trac Trac
Trac Trac<=0.11.2.1
Trac Trac=0.5
Trac Trac=0.5.1
Trac Trac=0.5.2
Trac Trac=0.6
Trac Trac=0.6.1
Trac Trac=0.7
Trac Trac=0.7.1
Trac Trac=0.8
Trac Trac=0.8.1
Trac Trac=0.8.2
Trac Trac=0.8.3
Trac Trac=0.8.4
Trac Trac=0.9
Trac Trac=0.9-b1
Trac Trac=0.9-b2
Trac Trac=0.9.1
Trac Trac=0.9.2
Trac Trac=0.9.3
Trac Trac=0.9.4
Trac Trac=0.9.5
Trac Trac=0.9.6
Trac Trac=0.10
Trac Trac=0.10.1
Trac Trac=0.10.2
Trac Trac=0.10.3
Trac Trac=0.10.3.1
Trac Trac=0.10.4
Trac Trac=0.10.5
Trac Trac=0.11
Trac Trac=0.11.2
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/Tracto a version that resolves this vulnerability.Fixed in 0.11.2
Event History
Dec 17, 2008
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Data Sourced
via NVD·06:30 PM
DescriptionSeverityAffected Software
May 17, 2022
Advisory Published
via GitHub·02:17 AM
Frequently Asked Questions
1
What is the severity of CVE-2008-5646?
CVE-2008-5646 is considered a denial of service vulnerability that can impact the availability of Trac.
2
How do I fix CVE-2008-5646?
To fix CVE-2008-5646, upgrade Trac to version 0.11.2 or later.
3
What versions of Trac are affected by CVE-2008-5646?
CVE-2008-5646 affects all versions of Trac prior to 0.11.2.
4
What impact does CVE-2008-5646 have on Trac installations?
CVE-2008-5646 can lead to a denial of service, making Trac unavailable to users.
5
Is there a workaround for CVE-2008-5646?
There are no known workarounds for CVE-2008-5646; upgrading is the recommended action.