CVE-2017-5137
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. An attacker could request and download the SMS logs from an unauthenticated perspective.
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 an unauthenticated information disclosure vulnerability allowing attackers to directly request and download SMS logs without any authentication credentials. The SMS log download function lacks access control checks, exposing sensitive communication data to anyone with network access to the device.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 admin interface or check the device label to confirm it is a SendQuick Entera or SendQuick Avera SMS Gateway applianceAffected if The device is a SendQuick Entera or Avera model
-
Check the installed firmware versionNavigate to the device admin panel system settings or firmware information page, or use the command line interface if available, to retrieve the current firmware version numberAffected if The firmware version is earlier than 2HF16 or the version cannot be determined (all versions before 2HF16 are affected)
-
Locate the SMS log download functionExamine the device web interface for links or menu options related to SMS logs, messaging archives, or communication records - typically found under logs, reports, or messaging sectionsAffected if The SMS log download feature exists and is accessible in the interface
-
Test unauthenticated access to SMS logsAttempt to access the SMS log download URL or function directly via browser or curl command without providing any login credentials or session tokenAffected if The SMS logs can be downloaded or viewed without any authentication required
-
Verify sensitive data exposureReview any accessed SMS logs to confirm they contain sensitive communication content such as phone numbers, message content, and timestampsAffected if The downloaded logs contain actual SMS message data and metadata without requiring authentication
The environment is affected if the device is a SendQuick Entera or Avera SMS Gateway running firmware earlier than version 2HF16 and the SMS log download function is accessible without authentication.
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 dataUpgrade affected devices to firmware version 2HF16 or later. If immediate patching is not feasible, implement network segmentation and firewall rules to restrict unauthorized access to the device management interfaces.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5137 — 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-5137 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