| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Sawmill Enterprise 8.7.9. The impacted element is an unknown function. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2017-5496. The attack must be initiated from a local position. Furthermore, there is an exploit available.
Details
A vulnerability was found in Sawmill Enterprise 8.7.9. It has been classified as problematic. This affects an unknown code. 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, integrity, and availability. The summary by CVE is:
Sawmill Enterprise 8.7.9 allows remote attackers to gain login access by leveraging knowledge of a password hash.
The bug was discovered 02/18/2017. The weakness was shared 02/18/2017 by John Page (hyp3rlinx) as Sawmill Enterprise v8.7.9 Pass The Hash Authentication Bypass as not defined mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. This vulnerability is uniquely identified as CVE-2017-5496 since 01/15/2017. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at Exploit-DB (41395). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.1
VulDB Base Score: 4.9
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
OpenVAS ID: 103382
OpenVAS Name: Sawmill Authentication Bypass Vulnerability
OpenVAS File: 🔍
OpenVAS Family: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/15/2017 🔍02/18/2017 🔍
02/18/2017 🔍
02/24/2017 🔍
03/15/2017 🔍
07/01/2017 🔍
09/02/2020 🔍
Sources
Advisory: Sawmill Enterprise v8.7.9 Pass The Hash Authentication BypassResearcher: John Page (hyp3rlinx)
Status: Not defined
CVE: CVE-2017-5496 (🔍)
GCVE (CVE): GCVE-0-2017-5496
GCVE (VulDB): GCVE-100-97269
OSVDB: - CVE-2017-5496 - Sawmill Enterprise - Authentication Bypass Issue
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/24/2017 16:09Updated: 09/02/2020 12:50
Changes: 02/24/2017 16:09 (62), 09/02/2020 12:50 (6)
Complete: 🔍
Cache ID: 216::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.