CVE-2013-2324: Critical severity hp storage data protector vulnerability
Published Jun 6, 2013
·Updated
Unspecified vulnerability in HP Storage Data Protector 6.20, 6.21, 7.00, and 7.01 allows remote attackers to execute arbitrary code via unknown vectors, aka ZDI-CAN-1629.
Affected Software
22 affected components
HP Storage Data Protector Hp-ux=6.20
HP Storage Data Protector Redhat Enterprise Linux=6.20
HP Storage Data Protector Sunos=6.20
HP Storage Data Protector Suse Linux=6.20
HP Storage Data Protector Windows Server 2003=6.20
HP Storage Data Protector Windows Server 2008=6.20
HP Storage Data Protector Hp-ux=6.21
HP Storage Data Protector Redhat Enterprise Linux=6.21
HP Storage Data Protector Sunos=6.21
HP Storage Data Protector Suse Linux=6.21
HP Storage Data Protector Windows Server 2003=6.21
HP Storage Data Protector Windows Server 2008=6.21
HP Storage Data Protector Hp-ux=7.00
HP Storage Data Protector Redhat Enterprise Linux=7.00
HP Storage Data Protector Suse Linux=7.00
HP Storage Data Protector Windows Server 2003=7.00
HP Storage Data Protector Windows Server 2008=7.00
HP Storage Data Protector Hp-ux=7.01
HP Storage Data Protector Redhat Enterprise Linux=7.01
HP Storage Data Protector Suse Linux=7.01
HP Storage Data Protector Windows Server 2003=7.01
HP Storage Data Protector Windows Server 2008=7.01
Event History
Jun 6, 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-2324?
CVE-2013-2324 is classified as a high severity vulnerability due to its ability to allow remote code execution.
2
How do I fix CVE-2013-2324?
To fix CVE-2013-2324, users should upgrade their HP Storage Data Protector to a version that has addressed the vulnerability.
3
What versions of HP Storage Data Protector are affected by CVE-2013-2324?
The affected versions of HP Storage Data Protector include 6.20, 6.21, 7.00, and 7.01.
4
What types of attacks does CVE-2013-2324 facilitate?
CVE-2013-2324 facilitates arbitrary code execution attacks by remote attackers.
5
Is there a workaround for CVE-2013-2324?
No specific workaround for CVE-2013-2324 has been publicly documented; upgrading to a patched version is recommended.