CVE-2024-7587
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 · uneditedIncorrect Default Permissions vulnerability in GenBroker32, which is included in the installers for Mitsubishi Electric GENESIS64 versions 10.97.3 and prior, Mitsubishi Electric Iconics Digital Solutions GENESIS64 versions 10.97.3 and prior, Mitsubishi Electric ICONICS Suite versions 10.97.3 and prior, Mitsubishi Electric Iconics Digital Solutions ICONICS Suite versions 10.97.3 and prior, Mitsubishi Electric GENESIS32 versions 9.70.300.23 and prior, Mitsubishi Electric Iconics Digital Solutions GENESIS32 versions 9.70.300.23 and prior, and Mitsubishi Electric MC Works64 all versions allows a local authenticated attacker to disclose or tamper with confidential information and data contained in the products, or cause a denial of service (DoS) condition on the products, by accessing a folder with incorrect permissions, when GenBroker32 is installed on the same PC as GENESIS64, ICONICS Suite, MC Works64, or GENESIS32.
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 confidenceGenBroker32, a component included in Mitsubishi Electric GENESIS64, ICONICS Suite, GENESIS32, and MC Works64 installers, creates folders with overly permissive default access controls. A local authenticated attacker can exploit these incorrect file system permissions to read sensitive data, modify configuration or operational files, or cause denial of service by accessing these improperly protected directories.
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<= 10.97.3all versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check if an affected product is installedLook for installation directories of Mitsubishi Electric GENESIS64, ICONICS Suite, GENESIS32, or MC Works64. Check the installed version of Genesis64 by examining its version information (typically in Add/Remove Programs or the program's About dialog).Affected if Genesis64 version is 10.97.3 or lower, or MC Works64 of any version is installed.
-
Locate GenBroker32 component foldersSearch for folders or executables named GenBroker32 within the product installation directories. Common paths may include bin, runtime, or service folders under the main installation path.Affected if GenBroker32 component folders are found within the product installation.
-
Identify folders created by GenBroker32Examine directories that were created by the GenBroker32 process during or after installation. Look for newly created folders under the product installation path that may contain configuration, data, or log files.Affected if Folders created by GenBroker32 exist in the installation directory.
-
Inspect permissions on GenBroker32 foldersUse icacls or Get-Acl PowerShell cmdlets to view the access control list (ACL) on folders created by GenBroker32. Check for entries granting excessive permissions such as Everyone, Users, orAuthenticated Users with Full Control or Modify rights.Affected if Folders grant broad access to standard users or Everyone group (such as Full Control, Modify, or Write permissions to non-administrators).
-
Verify non-admin user accessAttempt to access the GenBroker32 folders using a standard (non-administrator) Windows account. Use commands like dir or access attempts to confirm if unprivileged users can read, modify, or delete files in these directories.Affected if Standard user accounts can read or modify files in GenBroker32-created folders.
A user is affected if their system has Genesis64 (version 10.97.3 or lower) or MC Works64 installed AND the folders created by GenBroker32 grant excessive permissions to standard users, allowing unprivileged account access to sensitive configuration or operational 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 dataReview and restrict file system permissions on folders created by GenBroker32 to follow least-privilege principles, ensuring only authorized administrators and services have access. Apply vendor-provided security patches or updates that correct the default permission settings.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7587 — 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-2024-7587 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