# CVE-2017-17763: Other in n/a

> SuperBeam lacks integrity protection during file transfers, allowing attackers to inject malicious APKs via crafted files.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Dec 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-x22f-393p-7w6f

## What is CVE-2017-17763?

CVE-2017-17763 is a high-severity vulnerability in n/a, published on 19 Dec 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SuperBeam through 4.1.3, when using the LAN or WiFi Direct Share feature, does not use HTTPS or any integrity-protection mechanism for file transfer, which makes it easier for remote attackers to send crafted files, as demonstrated by APK injection.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Liveqos Superbeam.

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

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

## Is CVE-2017-17763 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17763 is a high-severity vulnerability in n/a, published on 19 Dec 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-17763 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-17763/ (Markdown: https://insights.sbomify.com/CVE-2017-17763/index.md)
```

## Sources

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

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