# CVE-2022-30275: Hardcoded credentials in n/a

> Attackers can read cleartext passwords from configuration files to bypass access controls and access protected industrial control projects.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wm34-q93c-vxx8

## What is CVE-2022-30275?

CVE-2022-30275 is a high-severity vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Motorola MOSCAD Toolbox software through 2022-05-02 relies on a cleartext password. It utilizes an MDLC driver to communicate with MOSCAD/ACE RTUs for engineering purposes. Access to these communications is protected by a password stored in cleartext in the wmdlcdrv.ini driver configuration file. In addition, this password is used for access control to MOSCAD/STS projects protected with the Legacy Password feature. In this case, an insecure CRC of the password is present in the project file: this CRC is validated against the password in the driver configuration file.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2022-30275?

It affects 1 product.


Products: Motorolasolutions Mdlc.

## How do I fix CVE-2022-30275?

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

## Is CVE-2022-30275 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-30273](https://insights.sbomify.com/CVE-2022-30273/): Weak cryptography in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-30275 and fix it if it is affected.

What it is: CVE-2022-30275 is a high-severity vulnerability in n/a, published on 26 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30275 in the wild and no public exploit code.

Affected product: n/a. 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-2022-30275/ (Markdown: https://insights.sbomify.com/CVE-2022-30275/index.md)
```

## Sources

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

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