# CVE-2018-18908: Information disclosure in n/a

> An attacker can intercept sensitive user data, including usernames, via Man-in-the-Middle attacks due to cleartext HTTP usage in the Sky Go Desktop application.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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:** 19 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-j7c8-cjw7-m5fm

## What is CVE-2018-18908?

CVE-2018-18908 is a medium-severity vulnerability in n/a, published on 19 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Sky Go Desktop application 1.0.19-1 through 1.0.23-1 for Windows performs several requests over cleartext HTTP. This makes the data submitted in these requests prone to Man in The Middle (MiTM) attacks, whereby an attacker would be able to obtain the data sent in these requests. Some of the requests contain potentially sensitive information that could be useful to an attacker, such as the victim's Sky username.

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

## Which versions are affected by CVE-2018-18908?

It affects 1 product.


Products: Sky Sky Go.

## How do I fix CVE-2018-18908?

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

## Is CVE-2018-18908 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18908 and fix it if it is affected.

What it is: CVE-2018-18908 is a medium-severity vulnerability in n/a, published on 19 Jan 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-2018-18908 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-2018-18908/ (Markdown: https://insights.sbomify.com/CVE-2018-18908/index.md)
```

## Sources

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

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