CVE-2013-5032: Critical severity phlymail vulnerability
Published Jan 12, 2014
·Updated
Unspecified vulnerability in Atmail before 6.6.4, and 7.x before 7.1.2, has unknown impact and attack vectors, a different vulnerability than CVE-2013-5031, CVE-2013-5033, and CVE-2013-5034.
Affected Software
26 affected components
Atmail atmail<=6.6.3
Atmail atmail=6.3.0
Atmail atmail=6.3.1
Atmail atmail=6.3.2
Atmail atmail=6.3.3
Atmail atmail=6.3.4
Atmail atmail=6.3.5
Atmail atmail=6.3.6
Atmail atmail=6.4.0
Atmail atmail=6.4.1
Atmail atmail=6.4.2
Atmail atmail=6.5.0
Atmail atmail=6.6.0
Atmail atmail=6.6.1
Atmail atmail=6.6.2
Atmail atmail=6.20.4
Atmail atmail=6.20.5
Atmail atmail=6.20.6
Atmail atmail=6.20.7
Atmail atmail=6.20.8
Atmail atmail=6.20.10
Atmail atmail=6.20.11
Atmail atmail=6.20.12
Atmail atmail=6.20.13
Atmail atmail=7.1.0
Atmail atmail=7.1.1
Event History
Jan 12, 2014
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2013-5032?
The severity level of CVE-2013-5032 has not been specified.
2
Which versions of Atmail are affected by CVE-2013-5032?
CVE-2013-5032 affects Atmail versions prior to 6.6.4 and 7.x before 7.1.2.
3
How do I fix CVE-2013-5032?
To fix CVE-2013-5032, upgrade to Atmail version 6.6.4 or 7.1.2 or later.
4
Is there a documented exploit for CVE-2013-5032?
There is no publicly available information regarding specific exploits for CVE-2013-5032.
5
What organization issued the CVE-2013-5032 vulnerability?
CVE-2013-5032 was issued by the Common Vulnerabilities and Exposures (CVE) system.