# CVE-2018-7295: Other in n/a

> Man-in-the-middle attackers can steal user credentials by intercepting unencrypted global.js requests in the Final Fantasy XIV launcher.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gj56-gxxr-68v5

## What is CVE-2018-7295?

CVE-2018-7295 is a high-severity vulnerability in n/a, published on 23 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ffxivlauncher.exe in Square Enix Final Fantasy XIV 4.21 and 4.25 on Windows is affected by Improper Enforcement of Message Integrity During Transmission in a Communication Channel, allowing a man-in-the-middle attacker to steal user credentials because a session retrieves global.js via http before proceeding to use https. This is fixed in Patch 4.3.

Weakness: CWE-924 (Improper Enforcement of Message Integrity During Transmission in a Communication Channel)

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

It affects 1 product.


Products: Square-Enix Final Fantasy Xiv.

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

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

## Is CVE-2018-7295 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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