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

> An attacker with local access can retrieve admin credentials from the configuration file to gain unauthorized access to video recordings and system settings.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8gcr-v287-2xpv

## What is CVE-2022-30018?

CVE-2022-30018 is a high-severity vulnerability in n/a, published on 19 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mobotix Control Center (MxCC) through 2.5.4.5 has Insufficiently Protected Credentials, Storing Passwords in a Recoverable Format via the MxCC.ini config file. The credential storage method in this software enables an attacker/user of the machine to gain admin access to the software and gain access to recordings/recording locations.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Mobotix Mxcontrolcenter.

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

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

## Is CVE-2022-30018 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30018 is a high-severity vulnerability in n/a, published on 19 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-30018 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-30018/ (Markdown: https://insights.sbomify.com/CVE-2022-30018/index.md)
```

## Sources

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

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