Skip to main content
Mallory
CriticalVulnerability

CVE-2017-5496: Authentication Bypass via Password Hash in Sawmill Enterprise 8.7.9

Published Mar 15, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3
EPSS5.8%93rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Sawmill
IdentifiersCVE-2017-5496CWE-257

Sawmill Enterprise 8.7.9 contains a vulnerability that allows remote attackers to gain login access by leveraging knowledge of a password hash. The authentication mechanism does not properly protect against the use of password hashes for direct authentication, enabling attackers who obtain a valid hash to bypass normal password verification and gain unauthorized access.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker with knowledge of a valid password hash can authenticate as the corresponding user, potentially gaining administrative or privileged access to the Sawmill Enterprise instance. This can lead to full compromise of the application, exposure of sensitive data, and further attacks within the environment.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the Sawmill Enterprise interface to trusted networks, monitor for suspicious login attempts, and rotate all user passwords if a hash leak is suspected. Implement strong password policies and consider additional authentication mechanisms such as multi-factor authentication where possible.

Remediation

Patch, then assume compromise.

Upgrade to a version of Sawmill Enterprise in which the authentication mechanism is fixed to prevent the use of password hashes for direct login. Ensure that password hashes are never accepted as credentials and that proper password verification is enforced.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SawmillSawmillapplication
FAQ

Frequently asked questions

Is CVE-2017-5496 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2017-5496 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2017-5496?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2017-5496. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2017-5496?
Upgrade to a version of Sawmill Enterprise in which the authentication mechanism is fixed to prevent the use of password hashes for direct login. Ensure that password hashes are never accepted as credentials and that proper password verification is enforced.
What products are affected by CVE-2017-5496?
Sawmill.
How severe is CVE-2017-5496?
CVE-2017-5496 has a CVSS v3 score of 9.8 (Critical) and an EPSS score of 5.8% (93rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.