# CVE-2024-23943: MB connect line: Cloud API access due to a lack of authentication for a critical function

> Unauthenticated attackers can access the cloud API of MB connect line devices due to missing authentication on a critical function.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 18 Mar 2025
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-8qm4-cq94-2553

## What is CVE-2024-23943?

CVE-2024-23943 is a critical missing authorization vulnerability in mbCONNECT24, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote attacker can gain access to the cloud API due to a lack of authentication for a critical function in the affected devices. Availability is not affected.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-23943?


## How do I fix CVE-2024-23943?

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

## Is CVE-2024-23943 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23943 and fix it if it is affected.

What it is: CVE-2024-23943 is a critical missing authorization vulnerability in mbCONNECT24, published on 18 Mar 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-2024-23943 in the wild and no public exploit code.

Affected product: mbCONNECT24. 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-2024-23943/ (Markdown: https://insights.sbomify.com/CVE-2024-23943/index.md)
```

## Sources

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

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