# CVE-2025-6074: Authentication Bypass to the MQTT configuration Web Interface

> Attackers with source code access can bypass authentication on the REST interface to read MQTT configuration data in ABB RMC-100 devices.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Jul 2025
- **Updated:** 3 Jul 2025
- **Also known as:** GHSA-2f3f-xhh3-hqgg

## What is CVE-2025-6074?

CVE-2025-6074 is a medium-severity vulnerability in ABB RMC-100, published on 3 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of Hard-coded Cryptographic Key vulnerability in ABB RMC-100, ABB RMC-100 LITE.

When the REST interface is enabled by the user, and an attacker gains access to
source code and control network, the attacker can bypass the REST interface authentication and gain access to MQTT configuration data.

This issue affects RMC-100: from 2105457-043 through 2105457-045; RMC-100 LITE: from 2106229-015 through 2106229-016.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2025-6074?


## How do I fix CVE-2025-6074?

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

## Is CVE-2025-6074 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6074 and fix it if it is affected.

What it is: CVE-2025-6074 is a medium-severity vulnerability in ABB RMC-100, published on 3 Jul 2025. 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-2025-6074 in the wild and no public exploit code.

Affected product: ABB RMC-100. 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-2025-6074/ (Markdown: https://insights.sbomify.com/CVE-2025-6074/index.md)
```

## Sources

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

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