dbcve.org
A320 XApplication · Flightsimlabs

CVE-2018-7259

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The FSX / P3Dv4 installer 2.0.1.231 for Flight Sim Labs A320-X sends a user's Google account credentials to http://installLog.flightsimlabs.com/LogHandler3.ashx if a pirated serial number has been entered, which allows remote attackers to obtain sensitive information, e.g., by sniffing the network for cleartext HTTP traffic. This behavior was removed in 2.0.1.232.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FSX/P3Dv4 installer version 2.0.1.231 for Flight Sim Labs A320-X contains credential exfiltration functionality that intercepts Google account credentials entered during installation when a pirated serial number is detected, then transmits these credentials in cleartext HTTP to a remote server (installLog.flightsimlabs.com/LogHandler3.ashx). Network-based attackers can capture these credentials by sniffing unencrypted HTTP traffic.

MitigationImmediately update to version 2.0.1.232 or later. Users who entered Google credentials during installation with a pirated serial should treat the credentials as compromised—rotate passwords, enable 2FA, and review account activity for unauthorized access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
A320 XApplication
Affected:= 2.0.1.231

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed A320-X product version
    Open your flight simulator (FSX or P3Dv4) and check the version of the A320-X addon in the aircraft selection menu or addon manager. Alternatively, check the file version of the A320-X executable in the installation folder.
    Affected if The product version shows 2.0.1.231 was installed (though note this is the installer version, not necessarily the product version)
  2. Review installer logs for malicious URL
    Search the flight simulator logs folder (typically in Documents or the product install directory) for any log files containing 'installLog.flightsimlabs.com' or 'LogHandler3.ashx'. Use a text search tool to find these strings in all .log files.
    Affected if Logs contain references to the URL installLog.flightsimlabs.com/LogHandler3.ashx, indicating the exfiltration endpoint was contacted
  3. Check network traffic logs for cleartext HTTP
    If you have network monitoring logs or a firewall log from around the time of installation, search for HTTP (port 80) connections to flightsimlabs.com domains transmitting data in cleartext.
    Affected if Cleartext HTTP traffic to installLog.flightsimlabs.com was recorded during the installation period
  4. Verify if pirated serial was used during install
    Recall or check installation notes/configuration files to determine if a non-official/pirated serial key was entered during the A320-X installation process.
    Affected if A pirated serial number was used AND the vulnerable installer version 2.0.1.231 was run

You are affected if you installed A320-X using installer version 2.0.1.231, entered a pirated serial key, and entered Google credentials during that installation, the credentials were likely transmitted in cleartext to a remote server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately update to version 2.0.1.232 or later. Users who entered Google credentials during installation with a pirated serial should treat the credentials as compromised—rotate passwords, enable 2FA, and review account activity for unauthorized access.

Recommended fix High confidence

2.0.1.232 or later

  1. Download the latest version of Flight Sim Labs A320-X installer (version 2.0.1.232 or later) from the official vendor website
  2. Uninstall the current version 2.0.1.231 from your system
  3. Install the new version 2.0.1.232 or latest available version
  4. Verify the installation was successful and the application runs normally
  5. Ensure any future installations use HTTPS-enabled connections or verified download sources

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in A320 X Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-7259 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data