dbcve.org
Maxicharger Ac Elite Business C50 FirmwareOperating system · Autel

CVE-2024-23958

HIGH · 8.8 CVSS v3.1 Published 2024-09-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Autel MaxiCharger AC Elite Business C50 BLE Hardcoded Credentials Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of Autel MaxiCharger AC Elite Business C50 charging stations. Authentication is not required to exploit this vulnerability. The specific flaw exists within the BLE AppAuthenRequest command handler. The handler uses hardcoded credentials as a fallback in case of an authentication request failure. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-23196

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Autel MaxiCharger AC Elite Business C50 contains a BLE authentication bypass vulnerability in the AppAuthenRequest command handler. The handler implements hardcoded credentials as a fallback mechanism when authentication requests fail, allowing any BLE-capable device within range to bypass authentication entirely and gain unauthorized access to the charging station's control functions.

MitigationApply vendor-supplied firmware patches when available; otherwise, disable BLE remote access features or implement strict physical access controls to prevent unauthorized BLE proximity. Consider network segmentation to isolate charging station infrastructure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Maxicharger Ac Elite Business C50 FirmwareOperating system
Affected:= 1.32.00

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Locate the charging station and verify it is an Autel MaxiCharger AC Elite Business C50 model. Check the physical device label or consult the device inventory/asset management system.
    Affected if The device is an Autel MaxiCharger AC Elite Business C50 and firmware version is 1.32.00
  2. Check the installed firmware version
    Access the device management interface (local display, mobile app, or admin web portal) and navigate to the firmware or software version information section. Record the firmware version number.
    Affected if The installed firmware version is exactly 1.32.00
  3. Verify BLE connectivity is enabled
    Attempt to scan for BLE advertisements from the device using a BLE scanner app or tool (such as nRF Connect or BLE debugging software) from a nearby BLE-capable device. Confirm whether the charging station is broadcasting BLE beacon signals.
    Affected if BLE is active and the device is broadcasting BLE signals, making it reachable within BLE range
  4. Test BLE authentication response
    Using a BLE sniffer or penetration testing tool capable of sending raw BLE GATT commands, attempt to connect to the charging station and send an AppAuthenRequest command with invalid credentials to observe if the fallback hardcoded credentials grant access.
    Affected if The device accepts authentication bypass through the hardcoded fallback credentials in the AppAuthenRequest handler

You are affected if the device is an Autel MaxiCharger AC Elite Business C50 running firmware version 1.32.00 with BLE functionality enabled and accessible within proximity.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patches when available; otherwise, disable BLE remote access features or implement strict physical access controls to prevent unauthorized BLE proximity. Consider network segmentation to isolate charging station infrastructure.

Fix this in Maxicharger Ac Elite Business C50 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23958 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23958 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data