CVE-2017-10818
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 · uneditedMaLion for Windows and Mac versions 3.2.1 to 5.2.1 uses a hardcoded cryptographic key which may allow an attacker to alter the connection settings of Terminal Agent and spoof the Relay Service.
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 confidenceMaLion versions 3.2.1 to 5.2.1 for Windows and Mac contains a hardcoded cryptographic key embedded in the application binary. An attacker with access to this key can modify the connection settings of the Terminal Agent component and impersonate the Relay Service, allowing man-in-the-middle attacks or redirection of traffic to malicious servers.
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>= 3.2.1, <= 5.2.1CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed MaLion versionLocate the MaLion application on the system (typically in Program Files on Windows or Applications folder on Mac) and check the version information. In Windows, right-click the executable and select Properties > Details to view the File Version. On Mac, right-click the app > Get Info or run 'mdls' command on the application bundle.Affected if The version falls within the range 3.2.1 to 5.2.1 inclusive.
-
Locate MaLion binary filesSearch for MaLion executable files - typically named 'MaLion.exe' (Windows) or 'MaLion.app' (Mac). On Windows, common paths include C:\Program Files\MaLion\ or C:\Program Files (x86)\MaLion\. On Mac, check /Applications/ for MaLion.app.Affected if The binary files exist and the version check shows the affected version range.
-
Inspect binary for embedded cryptographic materialUse a hex editor or strings utility to examine the MaLion executable. On Windows, run 'strings MaLion.exe | findstr -i key' or open the binary in a hex editor to search for cryptographic patterns (look for long hexadecimal strings that may be AES keys, RSA keys, or similar). On Mac, use 'strings MaLion.app/Contents/MacOS/MaLion | grep -i key' or the hex editor approach.Affected if Hardcoded cryptographic key material (long hex strings, PEM-like headers, or Base64-encoded keys) is found embedded in the binary.
-
Check Terminal Agent configurationLocate configuration files for the Terminal Agent component. Look in the MaLion installation directory for files named 'config', 'settings', or 'terminal' with extensions like .xml, .ini, .json, or .conf. Search for connection-related settings.Affected if Terminal Agent configuration exists and contains hardcoded connection settings or references to a static cryptographic key.
-
Verify Relay Service connection settingsExamine configuration files for Relay Service endpoint URLs and any associated authentication or encryption settings. Check for settings that specify relay server addresses or tunnel configurations.Affected if Relay Service is configured and connection settings use embedded or static key material rather than dynamic authentication.
You are affected if MaLion version 3.2.1 through 5.2.1 is installed AND a hardcoded cryptographic key is found embedded in the application binary or configuration files used by the Terminal Agent component.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataReplace the hardcoded cryptographic key with dynamic key management using secure secret storage (e.g., OS credential stores, environment variables, or hardware security modules), and implement proper key derivation or certificate pinning for Relay Service communication.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10818 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-10818 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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