CVE-2013-2329: Critical severity HP Storage Data Protector Hp-ux 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-1637.
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-2329?
CVE-2013-2329 is rated as a critical vulnerability due to its potential to allow remote arbitrary code execution.
2
How do I fix CVE-2013-2329?
To fix CVE-2013-2329, you should update HP Storage Data Protector to the latest version that addresses the vulnerability.
3
Which software versions are affected by CVE-2013-2329?
Versions 6.20, 6.21, 7.00, and 7.01 of HP Storage Data Protector are affected by CVE-2013-2329.
4
Can CVE-2013-2329 be exploited remotely?
Yes, CVE-2013-2329 can be exploited remotely, allowing attackers to execute arbitrary code on affected systems.
5
Is there any workaround for CVE-2013-2329?
No official workaround is provided for CVE-2013-2329; the recommended action is to apply the necessary updates.