# CVE-2024-39886: Information disclosure in TONE store App

> Man-in-the-middle attackers can intercept and modify cleartext communications between the TONE store mobile app and its website.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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:** 10 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4qfq-632q-hr28

## What is CVE-2024-39886?

CVE-2024-39886 is a low-severity vulnerability in DREAM TRAIN INTERNET INC. TONE store App, published on 10 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TONE store App version 3.4.2 and earlier contains an issue with unprotected primary channel. Since TONE store App communicates with TONE store website in cleartext, a man-in-the-middle attack may allow an attacker to obtain and/or alter communications of the affected App.

Weakness: CWE-419 (Unprotected Primary Channel)

## Which versions are affected by CVE-2024-39886?


## How do I fix CVE-2024-39886?

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

## Is CVE-2024-39886 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39886 and fix it if it is affected.

What it is: CVE-2024-39886 is a low-severity vulnerability in DREAM TRAIN INTERNET INC. TONE store App, published on 10 Jul 2024. 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-2024-39886 in the wild and no public exploit code.

Affected product: DREAM TRAIN INTERNET INC. TONE store App. 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-2024-39886/ (Markdown: https://insights.sbomify.com/CVE-2024-39886/index.md)
```

## Sources

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

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