# CVE-2018-7822: Misconfiguration in SoMachine Basic and Modicon M221, SoMachine Basic, all versions Modicon M221, all references, all versions prior to firmware V1.10.0.0

> Incorrect default permissions allow unauthorized local users to access SoMachine Basic resource files, potentially exposing sensitive configuration data.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-652g-fx4g-24jw

## What is CVE-2018-7822?

CVE-2018-7822 is a medium-severity vulnerability in SoMachine Basic and Modicon M221, SoMachine Basic, all versions Modicon M221, all references, all versions prior to firmware V1.10.0.0, published on 22 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An 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.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2018-7822?

It affects 2 products.


Products: Schneider-Electric Modicon M221 Firmware, Schneider-Electric Somachine Basic.

## How do I fix CVE-2018-7822?

No fix has been published for CVE-2018-7822 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-7822 being exploited?

There is no known exploitation of CVE-2018-7822 in the wild and no public exploit code.

## Other vulnerabilities in SoMachine Basic and Modicon M221, SoMachine Basic, all versions Modicon M221, all references, all versions prior to firmware V1.10.0.0

- [CVE-2020-28214](https://insights.sbomify.com/CVE-2020-28214/): Weak cryptography in Modicon M221 (all references, all versions) (critical 9.8)
- [CVE-2018-7790](https://insights.sbomify.com/CVE-2018-7790/): Auth bypass in Modicon M221, all references, all versions prior to firmware V1.6.2.0 (critical 9.8)
- [CVE-2018-7791](https://insights.sbomify.com/CVE-2018-7791/): Auth bypass in Modicon M221, all references, all versions prior to firmware V1.6.2.0 (critical 9.8)
- [CVE-2018-7821](https://insights.sbomify.com/CVE-2018-7821/): Denial of service in SoMachine Basic and Modicon M221, SoMachine Basic, all versions Modicon M221, all references, all versions prior to firmware V1.10.0.0 (high 7.5)
- [CVE-2018-7792](https://insights.sbomify.com/CVE-2018-7792/): Weak cryptography in Modicon M221, all references, all versions prior to firmware V1.6.2.0 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7822 and fix it if it is affected.

What it is: CVE-2018-7822 is a medium-severity vulnerability in SoMachine Basic and Modicon M221, SoMachine Basic, all versions Modicon M221, all references, all versions prior to firmware V1.10.0.0, published on 22 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7822 in the wild and no public exploit code.

Affected product: SoMachine Basic and Modicon M221, SoMachine Basic, all versions Modicon M221, all references, all versions prior to firmware V1.10.0.0. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-7822/ (Markdown: https://insights.sbomify.com/CVE-2018-7822/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-7822
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-7822
- OSV: https://osv.dev/vulnerability/CVE-2018-7822

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-7822/
Summaries are generated and may contain mistakes; the official description above is the record.