# CVE-2017-5137: Information disclosure in n/a

> Unauthenticated attackers can download SMS logs from SendQuick Entera and Avera devices, exposing sensitive communication data.

- **Severity:** Medium 6.2 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-452r-r77c-2p69

## What is CVE-2017-5137?

CVE-2017-5137 is a medium-severity vulnerability in n/a, published on 5 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on SendQuick Entera and Avera devices before 2HF16. An attacker could request and download the SMS logs from an unauthenticated perspective.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2017-5137?

It affects 2 products.


Products: Sendquick Avera Sms Gateway Firmware, Sendquick Entera Sms Gateway Firmware.

## How do I fix CVE-2017-5137?

No fix has been published for CVE-2017-5137 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-5137 being exploited?

There is no known exploitation of CVE-2017-5137 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2016-10098](https://insights.sbomify.com/CVE-2016-10098/): Command injection in n/a (critical 9.8)
- [CVE-2017-5136](https://insights.sbomify.com/CVE-2017-5136/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-5137 and fix it if it is affected.

What it is: CVE-2017-5137 is a medium-severity vulnerability in n/a, published on 5 Feb 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-5137 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-5137/ (Markdown: https://insights.sbomify.com/CVE-2017-5137/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-5137
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-5137
- OSV: https://osv.dev/vulnerability/CVE-2017-5137

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-5137/
Summaries are generated and may contain mistakes; the official description above is the record.