# CVE-2019-9939: Auth bypass in n/a

> Remote attackers on the same network can bypass authentication in SHAREit for Android by requesting a non-existing page, adding their device to the trusted list.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 22 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gh6j-74ww-wq32

## What is CVE-2019-9939?

CVE-2019-9939 is a high-severity authentication bypass vulnerability in n/a, published on 22 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The SHAREit application before 4.0.36 for Android allows a remote attacker (on the same network or joining public "open" Wi-Fi hotspots created by the application when file transfer is initiated) to bypass authentication by trying to fetch a non-existing page. When the non-existing page is requested, the application responds with a 200 status code and empty page, and adds the requesting client device into the list of recognized devices.

## Which versions are affected by CVE-2019-9939?

It affects 1 product.


Products: Ushareit Shareit.

## How do I fix CVE-2019-9939?

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

## Is CVE-2019-9939 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-14941](https://insights.sbomify.com/CVE-2019-14941/): Denial of service in n/a (high 7.5)
- [CVE-2019-15234](https://insights.sbomify.com/CVE-2019-15234/): Denial of service in n/a (high 7.5)
- [CVE-2019-9938](https://insights.sbomify.com/CVE-2019-9938/): Missing authorization in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9939 and fix it if it is affected.

What it is: CVE-2019-9939 is a high-severity authentication bypass vulnerability in n/a, published on 22 Mar 2019. 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-2019-9939 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-2019-9939/ (Markdown: https://insights.sbomify.com/CVE-2019-9939/index.md)
```

## Sources

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

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