CVE-2017-5809
CVE-2017-5809 is a medium-severity vulnerability in Hp Data Protector with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-275.
Key facts
- Severity: Medium (CVSS 3.x base score 5.5)
- CVSS v2: 4.9
- EPSS exploit prediction: 2% (73rd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-275
- Affected product: Hp Data Protector
- Published:
- Last modified:
Description
A Remote Arbitrary Code Execution vulnerability in HPE Data Protector version prior to 8.17 and 9.09 was found.
Frequently asked questions
- What is CVE-2017-5809?
- A Remote Arbitrary Code Execution vulnerability in HPE Data Protector version prior to 8.17 and 9.09 was found.
- How severe is CVE-2017-5809?
- CVE-2017-5809 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
- Is CVE-2017-5809 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (73rd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2017-5809?
- CVE-2017-5809 primarily affects Hp Data Protector. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2017-5809?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2017-5809 published?
- CVE-2017-5809 was published on 2018-02-15 and last updated on 2026-06-17.
References
- http://www.securityfocus.com/bid/100088
- https://labs.mwrinfosecurity.com/assets/BlogFiles/mwri-setuid-bit-set-omniresolve-2017-08-02.pdf
- https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-hpesbgn03732en_us
Affected products (2)
- cpe:2.3:a:hp:data_protector:*:*:*:*:*:*:*:*
- cpe:2.3:a:hp:data_protector:9.09:*:*:*:*:*:*:*
More vulnerabilities in Hp Data Protector
- CVE-2011-0924 — Critical (CVSS 10.0): The client in HP Data Protector does not verify the contents of files associated with the EXEC_CMD command, which…
- CVE-2011-0923 — Critical (CVSS 10.0): The client in HP Data Protector does not properly validate EXEC_CMD arguments, which allows remote attackers to execute…
- CVE-2011-0922 — Critical (CVSS 10.0): The client in HP Data Protector allows remote attackers to execute arbitrary programs via an EXEC_SETUP command that…
- CVE-2011-0921 — Critical (CVSS 10.0): crs.exe in the Cell Manager Service in the client in HP Data Protector does not properly validate credentials…
- CVE-2017-5807 — Critical (CVSS 9.8): A Remote Arbitrary Code Execution vulnerability in HPE Data Protector version prior to 8.17 and 9.09 was found.
- CVE-2016-2008 — Critical (CVSS 9.8): HPE Data Protector before 7.03_108, 8.x before 8.15, and 9.x before 9.06 allows remote attackers to execute arbitrary…
All CVEs affecting Hp Data Protector →
Other CWE-275 vulnerabilities
- CVE-2017-6513 — Critical (CVSS 9.9): The WHMCS Reseller Module V2 2.0.2 in Softaculous Virtualizor before 2.9.1.0 does not verify the user correctly, which…
- CVE-2017-17060 — Critical (CVSS 9.8): OX Software GmbH OX App Suite 7.8.4 and earlier is affected by: Insecure Permissions.
- CVE-2017-16887 — Critical (CVSS 9.8): The portal on FiberHome Mobile WIFI Device Model LM53Q1 VH519R05C01S38 uses SOAP based web services in order to…
- CVE-2023-39399 — Critical (CVSS 9.1): Parameter verification vulnerability in the installd module. Successful exploitation of this vulnerability may cause…
- CVE-2023-39398 — Critical (CVSS 9.1): Parameter verification vulnerability in the installd module. Successful exploitation of this vulnerability may cause…
- CVE-2019-2177 — High (CVSS 8.8): In isPreferred of HidProfile.java in Android 7.1.1, 7.1.2, 8.0, 8.1 and 9, there is a possible device type confusion…