CVE-2013-3268: Critical severity Novell iManager vulnerability
Published Apr 24, 2013
·Updated
Novell iManager 2.7 before SP6 Patch 1 does not refresh a token after a logout action, which has unspecified impact and remote attack vectors.
Affected Software
17 affected components
Novell iManager<=2.7
Novell iManager=2.7-refresh6
Novell iManager=2.7-sp4
Novell iManager=2.7-sp4_patch1
Novell iManager=2.7-sp4_patch2
Novell iManager=2.7-sp4_patch3
Novell iManager=2.7-sp4_patch4
Novell iManager=2.7-sp5
Novell iManager=2.7.0
Novell iManager=2.7.1
Novell iManager=2.7.2
Novell iManager=2.7.3
Novell iManager=2.7.3-ftf2
Novell iManager=2.7.3-ftf4
Novell iManager=2.7.3-sp3
Novell iManager=2.7.4
Novell iManager=2.7.5
Event History
Apr 24, 2013
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2013-3268?
The severity of CVE-2013-3268 is classified as critical with a score of 10.
2
How do I fix CVE-2013-3268?
To fix CVE-2013-3268, you should upgrade to Novell iManager 2.7 SP6 Patch 1 or later.
3
What is the impact of CVE-2013-3268?
CVE-2013-3268 allows for potential unauthorized access due to the failure to refresh a token after a logout.
4
Which versions of Novell iManager are affected by CVE-2013-3268?
CVE-2013-3268 affects Novell iManager versions 2.7 before SP6 Patch 1.
5
Is there a workaround for CVE-2013-3268?
There are no known workarounds for CVE-2013-3268; applying the patch is recommended.