CVE-2017-5136
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 issue was discovered on SendQuick Entera and Avera devices before 2HF16. The application failed to check the access control of the request which could result in an attacker being able to shutdown the system.
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 confidenceSendQuick Entera and Avera devices before version 2HF16 contain a broken access control vulnerability where the application fails to validate authorization for certain requests, allowing unauthenticated or unauthorized attackers to remotely shut down the system.
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 dataall versionsall versionsCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 device modelAccess the device management interface or check device documentation/labels to confirm the model is SendQuick Entera SMS Gateway or SendQuick Avera SMS GatewayAffected if The device is a SendQuick Entera or Avera SMS Gateway
-
Determine the firmware versionLog into the device admin panel and navigate to the system status or firmware information page to view the current firmware version. Alternatively, check the firmware file name or device documentation.Affected if The firmware version is earlier than 2HF16 (such as 2HF15, 2HF14, or any version without the 2HF16 designation)
-
Verify management interface network exposureCheck firewall rules, router configurations, or network scans to determine if the device management interface (typically ports 80, 443, or custom HTTP/HTTPS ports) is accessible from untrusted networks or the internetAffected if The management interface is exposed to untrusted networks without VPN or IP restrictions
-
Check for unauthorized shutdown accessFrom an untrusted network perspective, attempt to send a shutdown or system control request to the device endpoint (common paths include /admin/shutdown, /cgi-bin/shutdown, or similar admin action URLs) using curl or a web browser without authenticationAffected if The device accepts and processes shutdown commands without requiring authentication credentials
A user is affected if they are running SendQuick Entera or Avera SMS Gateway firmware before version 2HF16 with the management interface accessible 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.
From vendor dataUpdate affected devices to firmware version 2HF16 or later. If immediate patching is not feasible, restrict network access to the management interface using firewall rules or VPN access controls.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5136 — 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-5136 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