# CVE-2019-7399: Other in n/a

> Man-in-the-middle attackers can intercept unencrypted HTTP requests for Terms of Use and Privacy pages on Amazon Fire OS devices.

- **Severity:** High 7.4 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g5q6-48ff-v986

## What is CVE-2019-7399?

CVE-2019-7399 is a high-severity vulnerability in n/a, published on 17 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Amazon Fire OS before 5.3.6.4 allows a man-in-the-middle attack against HTTP requests for "Terms of Use" and Privacy pages.

Weakness: CWE-346 (Origin Validation Error)

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

It affects 1 product.


Products: Amazon Fire Os.

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

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

## Is CVE-2019-7399 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7292](https://insights.sbomify.com/CVE-2015-7292/): Memory corruption in Amazon Fire OS before 2016-01-15 (critical 9.8)
- [CVE-2018-11019](https://insights.sbomify.com/CVE-2018-11019/): Denial of service in n/a (high 7.5)
- [CVE-2018-11021](https://insights.sbomify.com/CVE-2018-11021/): Denial of service in n/a (high 7.5)
- [CVE-2018-11022](https://insights.sbomify.com/CVE-2018-11022/): Denial of service in n/a (high 7.5)
- [CVE-2018-11023](https://insights.sbomify.com/CVE-2018-11023/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-7399 is a high-severity vulnerability in n/a, published on 17 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7399 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-7399/ (Markdown: https://insights.sbomify.com/CVE-2019-7399/index.md)
```

## Sources

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

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