CVE-2017-14728
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn authentication bypass was found in an unknown area of the SiteOmat source code. All SiteOmat BOS versions are affected, prior to the submission of this exploit. Also, the SiteOmat does not force administrators to switch passwords, leaving SSH and HTTP remote authentication open to public.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCVE-2017-14728 is a critical authentication bypass vulnerability in SiteOmat BOS that allows unauthorized access to the application. The vulnerability exists due to a flaw in the authentication mechanism that fails to properly validate credentials, combined with the system not enforcing password changes for default administrator accounts. This exposes both SSH and HTTP interfaces to public remote authentication, allowing attackers to gain full administrative access without legitimate credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.4.414.084CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SiteOmat installation and versionLocate the SiteOmat or Orpak Siteomat application on your system and determine its installed version number. This is typically found in the application's about screen, installation directory, or version file. Compare your version against the affected range of < 6.4.414.084Affected if The installed version is lower than 6.4.414.084
-
Verify default administrator account statusCheck whether default administrator accounts (such as 'admin', 'administrator', or 'root') exist on the system and determine if they are using default factory-set passwords that have not been changedAffected if Default admin accounts exist with unchanged default passwords
-
Inspect SSH interface exposureExamine network configuration and firewall rules to determine if the SSH service (typically port 22) on the SiteOmat server is accessible from untrusted or public networksAffected if SSH interface is reachable from public or untrusted networks without proper network filtering
-
Inspect HTTP/HTTPS interface exposureExamine network configuration and firewall rules to determine if the SiteOmat web interface (HTTP/HTTPS ports) is accessible from untrusted or public networksAffected if HTTP or HTTPS interface is reachable from public or untrusted networks without proper network filtering
A system is affected if it runs SiteOmat version lower than 6.4.414.084 with default admin passwords still active and SSH or HTTP interfaces exposed to untrusted networks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.4.414.084
Immediately restrict public access to SSH and HTTP interfaces via firewall rules or network segmentation. Force password changes for all default/admin accounts and implement proper authentication enforcement. Audit the codebase to identify and fix the specific authentication bypass mechanism.
6.4.414.084 or later
- 1. Verify the current SiteOmat version by accessing the system admin interface or checking system files
- 2. If version is below 6.4.414.084, initiate upgrade to version 6.4.414.084 or later
- 3. After upgrade, immediately change all default administrative passwords for both SSH and HTTP interfaces
- 4. Verify that the authentication bypass vulnerability is no longer present by testing unauthorized access attempts
- 5. Review and document all credential changes for compliance purposes
- 6. Implement a policy requiring mandatory password changes on first admin login post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14728 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-14728 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data