What is the severity of CVE-2013-2349?

CVE-2013-2349 is considered a high-severity vulnerability due to its potential for remote code execution and denial of service.

How do I fix CVE-2013-2349?

To mitigate CVE-2013-2349, ensure that you update HP Storage Data Protector to a fixed version as recommended by HP.

What versions are affected by CVE-2013-2349?

CVE-2013-2349 affects HP Storage Data Protector versions 6.20 and 6.21 on various operating systems, including Windows Server 2003 and 2008.

Can CVE-2013-2349 be exploited remotely?

Yes, CVE-2013-2349 can be exploited by remote attackers to execute arbitrary code or cause a denial of service.

Is there a workaround for CVE-2013-2349?

There are no known workarounds for CVE-2013-2349; updating to a secure version is the only effective solution.

Vulnerability/
CVE-2013-2349

critical

4/1/2014

9/10/2019

CVE-2013-2349

First published: Sat Jan 04 2014(Updated: )

Unspecified vulnerability in HP Storage Data Protector 6.2X allows remote attackers to execute arbitrary code or cause a denial of service via unknown vectors, aka ZDI-CAN-1896.

Credit: hp-security-alert@hp.com

Affected Software	Affected Version	How to fix
Hp Storage Data Protector	=6.20
Hp Storage Data Protector	=6.20
Hp Storage Data Protector	=6.20
Hp Storage Data Protector	=6.20
Hp Storage Data Protector	=6.20
Hp Storage Data Protector	=6.21
Hp Storage Data Protector	=6.21
Hp Storage Data Protector	=6.21
Hp Storage Data Protector	=6.21
Hp Storage Data Protector	=6.21

Never miss a vulnerability like this again

Reference Links

http://h20565.www2.hp.com/portal/site/hpsc/template.PAGE/public/kb/docDisplay/?docId=emr_na-c03822422

Frequently Asked Questions

What is the severity of CVE-2013-2349?
CVE-2013-2349 is considered a high-severity vulnerability due to its potential for remote code execution and denial of service.
How do I fix CVE-2013-2349?
To mitigate CVE-2013-2349, ensure that you update HP Storage Data Protector to a fixed version as recommended by HP.
What versions are affected by CVE-2013-2349?
CVE-2013-2349 affects HP Storage Data Protector versions 6.20 and 6.21 on various operating systems, including Windows Server 2003 and 2008.
Can CVE-2013-2349 be exploited remotely?
Yes, CVE-2013-2349 can be exploited by remote attackers to execute arbitrary code or cause a denial of service.
Is there a workaround for CVE-2013-2349?
There are no known workarounds for CVE-2013-2349; updating to a secure version is the only effective solution.

collector/nvd-index
agent/references
agent/severity
agent/author
agent/tags
agent/description
agent/type
agent/event
agent/first-publish-date
agent/softwarecombine
vendor/hp
canonical/hp storage data protector
version/hp storage data protector/6.20
version/hp storage data protector/6.21

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2013-2349?
CVE-2013-2349 is considered a high-severity vulnerability due to its potential for remote code execution and denial of service.
How do I fix CVE-2013-2349?
To mitigate CVE-2013-2349, ensure that you update HP Storage Data Protector to a fixed version as recommended by HP.
What versions are affected by CVE-2013-2349?
CVE-2013-2349 affects HP Storage Data Protector versions 6.20 and 6.21 on various operating systems, including Windows Server 2003 and 2008.
Can CVE-2013-2349 be exploited remotely?
Yes, CVE-2013-2349 can be exploited by remote attackers to execute arbitrary code or cause a denial of service.
Is there a workaround for CVE-2013-2349?
There are no known workarounds for CVE-2013-2349; updating to a secure version is the only effective solution.