What is the severity of CVE-2013-6195?

CVE-2013-6195 is classified as a high severity vulnerability due to its potential to allow remote code execution.

How do I fix CVE-2013-6195?

To resolve CVE-2013-6195, upgrade HP Storage Data Protector to the latest version that includes security patches.

What versions of HP Storage Data Protector are affected by CVE-2013-6195?

CVE-2013-6195 affects HP Storage Data Protector versions 6.20 and 6.21 on certain operating systems.

Can I exploit CVE-2013-6195 locally?

CVE-2013-6195 is primarily a remote vulnerability, meaning that it is exploited from a remote location rather than locally.

Is CVE-2013-6195 currently being actively exploited?

As of now, there is no public indication that CVE-2013-6195 is being actively exploited, but it remains a significant risk.

Vulnerability/
CVE-2013-6195

critical

4/1/2014

6/8/2024

CVE-2013-6195

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-2008.

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-6195?
CVE-2013-6195 is classified as a high severity vulnerability due to its potential to allow remote code execution.
How do I fix CVE-2013-6195?
To resolve CVE-2013-6195, upgrade HP Storage Data Protector to the latest version that includes security patches.
What versions of HP Storage Data Protector are affected by CVE-2013-6195?
CVE-2013-6195 affects HP Storage Data Protector versions 6.20 and 6.21 on certain operating systems.
Can I exploit CVE-2013-6195 locally?
CVE-2013-6195 is primarily a remote vulnerability, meaning that it is exploited from a remote location rather than locally.
Is CVE-2013-6195 currently being actively exploited?
As of now, there is no public indication that CVE-2013-6195 is being actively exploited, but it remains a significant risk.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/references
agent/severity
agent/last-modified-date
agent/description
agent/tags
agent/first-publish-date
agent/event
agent/source
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-6195?
CVE-2013-6195 is classified as a high severity vulnerability due to its potential to allow remote code execution.
How do I fix CVE-2013-6195?
To resolve CVE-2013-6195, upgrade HP Storage Data Protector to the latest version that includes security patches.
What versions of HP Storage Data Protector are affected by CVE-2013-6195?
CVE-2013-6195 affects HP Storage Data Protector versions 6.20 and 6.21 on certain operating systems.
Can I exploit CVE-2013-6195 locally?
CVE-2013-6195 is primarily a remote vulnerability, meaning that it is exploited from a remote location rather than locally.
Is CVE-2013-6195 currently being actively exploited?
As of now, there is no public indication that CVE-2013-6195 is being actively exploited, but it remains a significant risk.