CVE-2018-7822
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 · uneditedAn Incorrect Default Permissions (CWE-276) vulnerability exists in SoMachine Basic, all versions, and Modicon M221(all references, all versions prior to firmware V1.10.0.0) which could cause unauthorized access to SoMachine Basic resource files when logged on the system hosting SoMachine Basic.
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 confidenceA local file permission vulnerability (CWE-276) in SoMachine Basic and Modicon M221 allows unauthorized access to resource files due to incorrect default permissions. An attacker with local system access could potentially read or modify sensitive resource files hosted on the system.
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 dataall versions< 1.10.0.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Determine if SoMachine Basic is installedLook for SoMachine Basic installation directory on the system, typically under Program Files/Schneider Electric, or check for SoMachine Basic in the list of installed programs.Affected if SoMachine Basic is installed on the system (all versions are affected)
-
Identify the Modicon M221 firmware versionConnect to the Modicon M221 PLC device and check the firmware version through the device management interface or by querying the device directly for its firmware version information.Affected if The Modicon M221 firmware version is lower than 1.10.0.0
-
Locate resource files associated with SoMachine BasicIdentify the installation directory for SoMachine Basic and locate resource files such as project files, configuration files, or any data files stored within the installation folder.Affected if Resource files exist in the SoMachine Basic installation directory
-
Inspect file permissions on resource filesCheck the file system permissions (ACLs) on the identified resource files to determine if unauthorized local users have read or write access. On Windows, use icacls or right-click properties > Security to view permissions.Affected if Local users other than administrators or the owner have read or write permissions to sensitive resource files
The environment is affected if SoMachine Basic is installed (any version) or if the Modicon M221 firmware version is below 1.10.0.0, and resource files have overly permissive access controls allowing unauthorized local access.
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 data1.10.0.0
Update Modicon M221 firmware to V1.10.0.0 or later; for SoMachine Basic, review and restrict file permissions on resource files to prevent unauthorized access by local users.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7822 — 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-2018-7822 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