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

> The grandMA2 Light system uses a hardcoded root password, allowing attackers on the network to gain full administrative control.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-xm62-h33r-968q

## What is CVE-2022-30036?

CVE-2022-30036 is a high-severity vulnerability in n/a, published on 21 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MA Lighting grandMA2 Light has a password of root for the root account. NOTE: The vendor's position is that the product was designed for isolated networks. Also, the successor product, grandMA3, is not affected by this vulnerability.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Malighting Grandma2 Light Firmware.

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

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

## Is CVE-2022-30036 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30036 is a high-severity vulnerability in n/a, published on 21 Aug 2022. 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-2022-30036 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-30036/ (Markdown: https://insights.sbomify.com/CVE-2022-30036/index.md)
```

## Sources

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

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