# CVE-2024-23959: Memory corruption in MaxiCharger AC Elite Business C50

> Network-adjacent attackers can execute arbitrary code on Autel MaxiCharger AC Elite Business C50 stations via a stack-based buffer overflow in BLE handling.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2024
- **Updated:** 3 Oct 2024
- **Also known as:** GHSA-qc45-54hc-mx8p

## What is CVE-2024-23959?

CVE-2024-23959 is a high-severity memory corruption vulnerability in Autel MaxiCharger AC Elite Business C50, published on 28 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Autel MaxiCharger AC Elite Business C50 BLE AppChargingControl Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Autel MaxiCharger AC Elite Business C50 charging stations. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.

The specific flaw exists within the handling of the AppChargingControl BLE command. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the device.

Was ZDI-CAN-23194

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

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

It affects 1 product.


Products: Autel Maxicharger Ac Elite Business C50 Firmware.

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

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

## Is CVE-2024-23959 being exploited?

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

## Other vulnerabilities in Autel MaxiCharger AC Elite Business C50

- [CVE-2025-5827](https://insights.sbomify.com/CVE-2025-5827/): Memory corruption in Autel MaxiCharger AC Wallbox Commercial (high 8.8)
- [CVE-2025-5830](https://insights.sbomify.com/CVE-2025-5830/): Memory corruption in Autel MaxiCharger AC Wallbox Commercial (high 8.8)
- [CVE-2024-23957](https://insights.sbomify.com/CVE-2024-23957/): Memory corruption in MaxiCharger AC Elite Business C50 (high 8.8)
- [CVE-2024-7795](https://insights.sbomify.com/CVE-2024-7795/): Memory corruption in MaxiCharger AC Elite Business C50 (high 8.8)
- [CVE-2024-23967](https://insights.sbomify.com/CVE-2024-23967/): Memory corruption in MaxiCharger AC Elite Business C50 (high 8.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-23959 is a high-severity memory corruption vulnerability in Autel MaxiCharger AC Elite Business C50, published on 28 Sep 2024. 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-2024-23959 in the wild and no public exploit code.

Affected product: Autel MaxiCharger AC Elite Business C50. 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-23959/ (Markdown: https://insights.sbomify.com/CVE-2024-23959/index.md)
```

## Sources

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

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