# CVE-2019-8632: Information disclosure in Texture-Android

> An attacker in a privileged network position can intercept analytics data sent over HTTP instead of HTTPS by the Texture SDK.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5h32-9qx7-wcp5

## What is CVE-2019-8632?

CVE-2019-8632 is a medium-severity vulnerability in Apple Texture-Android, published on 18 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Some analytics data was sent using HTTP rather than HTTPS. This was addressed by no longer sending this analytics data. This issue is fixed in Texture 5.11.10 for iOS, Texture 4.22.0.4 for Android. An attacker in a privileged network position may be able to intercept analytics data.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Apple Texture.

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

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

## Is CVE-2019-8632 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-8632 is a medium-severity vulnerability in Apple Texture-Android, published on 18 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-8632 in the wild and no public exploit code.

Affected product: Apple Texture-Android. 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-8632/ (Markdown: https://insights.sbomify.com/CVE-2019-8632/index.md)
```

## Sources

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

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