HPE NonStop Server H/J/L SSH Service information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in HPE NonStop Server H/J/L. Affected by this issue is some unknown functionality of the component SSH Service. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2017-5803. It is possible to initiate the attack remotely. There is no exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as problematic has been found in HPE NonStop Server H/J/L. This affects an unknown code of the component SSH Service. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
A Remote Disclosure of Information vulnerability in HPE NonStop Servers using SSH Service version L series: T0801L02 through T0801L02^ABX; J and H series: T0801H01 through T0801H01^ACA was found.
The bug was discovered 04/27/2017. The weakness was shared 04/27/2017 by Daniel Correa as HPESBNS03735 as confirmed security bulletin (Website). The advisory is shared at h20565.www2.hpe.com. This vulnerability is uniquely identified as CVE-2017-5803 since 02/01/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at SecurityFocus (BID 98052†) and SecurityTracker (ID 1038370†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.hpe.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.0VulDB Meta Temp Score: 6.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (HPE): 5.3
Vendor Vector (HPE): 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Vendor Base Score (HPE): 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
02/01/2017 🔍04/27/2017 🔍
04/27/2017 🔍
04/27/2017 🔍
04/27/2017 🔍
04/28/2017 🔍
02/15/2018 🔍
09/21/2020 🔍
Sources
Vendor: hpe.comAdvisory: HPESBNS03735
Researcher: Daniel Correa
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2017-5803 (🔍)
GCVE (CVE): GCVE-0-2017-5803
GCVE (VulDB): GCVE-100-100629
SecurityFocus: 98052 - HP NonStop Servers CVE-2017-5803 Information Disclosure Vulnerability
OSVDB: - HPE NonStop Server informtation disclosure
SecurityTracker: 1038370
Entry
Created: 04/28/2017 09:05Updated: 09/21/2020 16:19
Changes: 04/28/2017 09:05 (79), 09/21/2020 16:19 (6)
Complete: 🔍
Cache ID: 216:599:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.