Severity:

HIGH RISK

(8.1)

Improper Authorization in Besen BS20 OTA Update

CVE-2026-9397

Deferred

Vulnerability type

Category:

Improper Authorization

CWE:

CWE-266, CWE-285

Impact:

Unauthorized Firmware or Configuration Modification

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Besen BS20 EV Charging Stations up to 20260426 contain an authorization weakness in the OTA (over-the-air) Update Installation Handler that can allow improperly authorized firmware or software updates to be installed.

Under certain complex remote conditions, an attacker may be able to manipulate the update process and bypass intended authorization checks, potentially altering device behavior.

Affected context

The vulnerability exists in the OTA Update Installation Handler of Besen BS20 EV Charging Stations when they accept and process remotely provided updates.

It is relevant in deployments where:

  • Devices are reachable from external networks or cloud update services
  • OTA update channels are active and configured
  • The device relies on internal logic to decide whether an update is permitted

Not all installations will expose the same level of risk; actual exploitability depends on network topology, update server configuration, and how authorization decisions are enforced.

Exploit preconditions

  • Attack surface: Remote, via the OTA update interface or associated backend communication channel.
  • Required access: Ability to interact with or influence the OTA update process (e.g., network position, control over or proximity to update traffic, or access to related services).
  • Trigger point: Submission or delivery of an update package or update request that is processed by the OTA Update Installation Handler.
  • Why exploitation is possible: Authorization checks for update installation are incomplete or improperly enforced (CWE-285/CWE-266), allowing certain update operations to proceed without the intended level of privilege verification or access control validation.
  • Complexity: Exploitation is described as difficult and high in complexity, likely requiring detailed knowledge of the update protocol, device behavior, and possibly timing or environmental conditions.

Why this happens

The core issue is an improper authorization design in the OTA update path.

Rather than strictly binding update installation to robust, consistently enforced access control decisions, the handler appears to rely on incomplete or insufficient checks around who or what is allowed to trigger or authorize an update.

This aligns with:

  • CWE-285: Improper Authorization – where the system does not correctly enforce access policies for protected actions (such as firmware installation).
  • CWE-266: Incorrect Privilege Assignment – where certain operations may be executed with more privilege than is appropriate, or where update operations are not constrained to the correct privilege level.

Abstractly, the pattern is that a high-impact operation (firmware or configuration update) is exposed through a remote interface without a rigorously enforced authorization boundary, creating room for unintended actors or contexts to trigger that operation.

Potential impact

  • An attacker may cause installation of unauthorized firmware or software updates.
  • Device configuration could be changed in ways that affect charging behavior, availability, or safety-related controls.
  • The charging station could be made unavailable (denial of service) through deployment of faulty or malicious updates.
  • Malicious firmware could enable further compromise of connected systems or use the device as a stepping stone within the network.
  • Tampering with billing- or metering-related logic could impact revenue integrity or reporting accuracy.

General mitigation guidance

Mitigation typically focuses on tightening authorization and trust boundaries around OTA updates:

  • Enforce strict, cryptographic validation of all update packages, binding them to trusted publishers and preventing installation of untrusted firmware.
  • Implement clear, centralized authorization decisions for update installation, ensuring that only well-defined, authenticated principals can trigger updates.
  • Separate privileges so that update download, verification, and installation use the least privilege necessary and are not implicitly authorized by network reachability alone.
  • Require multi-step or defense-in-depth controls for high-impact actions (e.g., ensuring both authentication and integrity checks are satisfied before installation proceeds).
  • Limit exposure of the OTA update interface through network segmentation, controlled endpoints, and secure communication channels to reduce who can even reach the update handler.

These patterns reduce the chance that a lapse in one layer of authorization results in successful unauthorized updates.

How teams detect issues like this

Detection efforts can concentrate on both code and operational behavior:

  • Static analysis & code review:
  • Look for update-related code paths that perform installation or critical changes without explicit, centralized authorization checks.
  • Identify any branches where update actions proceed on implicit trust (e.g., based solely on message origin or device state) rather than explicit privilege verification.
  • Review privilege boundaries to ensure that update handlers do not automatically inherit elevated rights without justification.
  • Configuration & policy review:
  • Examine deployment settings for OTA endpoints, ensuring access control policies and authentication mechanisms are correctly configured and enforced.
  • Validate that update signing and verification configurations cannot be bypassed or disabled without appropriate authorization.
  • Runtime monitoring:
  • Log and monitor all update attempts, including source, time, and outcome, to detect anomalous update activity.
  • Use alerting rules or SIEM integrations to flag unexpected or high-frequency update operations.
  • Automated security scanning and policy enforcement tools can be integrated into development and deployment pipelines to flag missing authorization checks around sensitive update operations.

Sources

SourceLink
github.comgithub.com/carfeii/besen#finding-4-unauthorized-firmware-installation-via-spoofed-ota-updates
vuldb.comvuldb.com/submit/813576
vuldb.comvuldb.com/vuln/365378
vuldb.comvuldb.com/vuln/365378/cti

Frequently asked

questions

Yes, the vulnerability affects the OTA update interface, which is designed for remote interaction. However, the original description emphasizes that the attack is high in complexity and difficult to exploit.

An attacker generally needs the ability to interact with or influence the OTA update process—such as reaching the relevant network interface, influencing update traffic, or abusing a related service. This is not typically possible to exploit from a casual external network position without additional conditions being met.

The safest approach is to enforce strong, explicit authorization and integrity checks on all update operations. This includes cryptographic signing and verification of update artifacts, robust authentication of update sources, and strict access control policies around who can initiate or approve installation.

Build OTA and other privileged operations around a security-by-design model: define clear authorization policies, centralize access control enforcement, apply least privilege to all update-related components, and routinely review these paths during security design reviews, code audits, and testing. Continuous integration checks for missing authorization logic in sensitive flows also help prevent regressions.

Find out what's already
exploitable in your codebase.