CVE-2017-12733
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 · uneditedA Missing Authentication for Critical Function issue was discovered in OPW Fuel Management Systems SiteSentinel Integra 100, SiteSentinel Integra 500, and SiteSentinel iSite ATG consoles with the following software versions: older than V175, V175-V189, V191-V195, and V16Q3.1. An attacker may create an application user account to gain administrative privileges.
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 · high confidenceMissing authentication in OPW Fuel Management Systems SiteSentinel consoles allows unauthenticated attackers to create application user accounts with administrative privileges. The vulnerability affects multiple console models across specific software version ranges, enabling complete system compromise without 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<= 175= 16q3.1= 189= 191= 195<= 175= 16q3.1= 189= 191= 195<= 175= 16q3.1= 189= 191= 195CVSS 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.0/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 the SiteSentinel console modelAccess the console web interface or check the device label/documentation to determine if the device is a SiteSentinel iSite ATG, Integra 500, or Integra 100 model.Affected if The device is any of these three SiteSentinel models.
-
Determine the installed firmware versionLog into the console admin interface and navigate to System Settings > About or Firmware Information to view the current firmware version. Alternatively, check the device firmware release notes or system logs.Affected if The firmware version is <= 175, = 16q3.1, = 189, = 191, or = 195.
-
Verify the user management interface is exposedConfirm that the console web interface (typically on port 80/443 or custom HTTP port) is reachable from the network. Attempt to access the user creation or account management page without authentication.Affected if The user creation interface is accessible without credentials.
-
Audit existing user accounts for unauthorized admin accountsReview the user list in the console under User Management or Account Settings. Look for any unexpected accounts with Administrative or Admin privileges that were not created by authorized personnel.Affected if Unexpected admin-level user accounts exist in the system.
-
Check system logs for account creation eventsExamine the console event logs or audit logs for entries indicating user account creation, especially those occurring at unexpected times or from unexpected sources.Affected if Log entries show user account creation without corresponding legitimate admin action.
A user is affected if they operate a SiteSentinel iSite ATG, Integra 500, or Integra 100 console running firmware version <= 175, = 16q3.1, = 189, = 191, or = 195, with the management interface network-accessible.
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.
From vendor dataUpdate affected consoles to vendor-provided patched versions (newer than V175, V196+, or V16Q3.2 depending on baseline). If immediate patching is not feasible, restrict network access to management interfaces and monitor for unauthorized account creation.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.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 $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12733 — 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-12733 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