CVE-2017-9638
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 · uneditedMitsubishi E-Designer, Version 7.52 Build 344 contains six code sections which may be exploited to overwrite the stack. This can result in arbitrary code execution, compromised data integrity, denial of service, and system crash.
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 · moderate confidenceMitsubishi E-Designer version 7.52 Build 344 contains stack-based buffer overflow vulnerabilities in six code sections where user-supplied input can overwrite the stack, enabling arbitrary code execution with the application's privileges. The vulnerability stems from insufficient bounds checking in the affected code paths, allowing attackers to overwrite return addresses and inject malicious payload.
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= 7.52CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify E-Designer installationCheck if Mitsubishi E-Designer is installed on the system. Common locations include C:\Program Files\Mitsubishi\E-Designer or C:\Program Files (x86)\Mitsubishi\E-Designer. Look for the eDesigner.exe executable.Affected if E-Designer version 7.52 is found on the system
-
Confirm installed version numberRight-click on the eDesigner.exe file, select Properties, and check the Version tab. Alternatively, open E-Designer and navigate to Help > About to view the version information.Affected if The version displayed is exactly 7.52 (any build within this version)
-
Check for project file handlingThe vulnerability is triggered when the application processes user-supplied input in project files. Observe if the application opens .eds or other project files without strict validation.Affected if The application processes untrusted project files using E-Designer version 7.52
-
Verify application is used with elevated privilegesCheck the user account running E-Designer. The vulnerability enables code execution with the application's privileges. Review the account's permission level in Task Manager or system settings.Affected if E-Designer 7.52 runs with administrative or high-privilege user rights
The environment is affected if Mitsubishi E-Designer version 7.52 is installed and processes user-supplied input such as project files.
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 dataApply vendor-supplied patch for E-Designer 7.52 or upgrade to a patched version; until then, restrict access to E-Designer, avoid opening untrusted project files, and run the application with least privilege in a isolated environment.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA5.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,216.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9638 — 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-9638 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