CVE intelligence and bounded remediation

CVE-2024-5684 — Vw Id.Charger Connect Firmware security vulnerability

High CVSS 8.8

An attacker with access to the private network (the charger is connected to) or local access to the Ethernet-Interface can exploit a faulty implementation of the JWT-library in order to bypass the password authentication to the web configuration interface and then has full access as the user would have. However, an attacker will not have developer or admin rights. If the implementation of the JWT-library is wrongly configured to accept "none"-algorithms, the server will pass insecure JWT. A local, unauthenticated attacker can exploit this vulnerability to bypass the authentication mechanism.

Severity
High
CVSS
8.8 (3.1)
Published
2024-06-06
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-345

Affected products

  • vw / id.charger_connect_firmware / spr3.2
  • vw / id.charger_connect_firmware / spr3.51
  • vw / id.charger_connect_firmware / spr3.52
  • vw / id.charger_pro_firmware / spr3.2
  • vw / id.charger_pro_firmware / spr3.51
  • vw / id.charger_pro_firmware / spr3.52

Matched remediation archetype

Supply-chain, dependency, build, and update integrity

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace affected packages, source archives, build actions, plugins, installers, and updates from declared source to deployed artifact.
  • Confirm provenance, signatures or digests, namespace ownership, lockfile resolution, registry configuration, and build-runner trust boundaries.
  • Inventory direct, transitive, vendored, generated, and bundled copies across releases and distribution channels.

Remediate safely

  • Move to a maintained trusted artifact or remove the dependency; pin immutable identities and verify provenance and integrity before use.
  • Regenerate lockfiles and artifacts in a clean isolated build, minimize build credentials and network access, and produce an updated software bill of materials.
  • Require reviewed update policy, protected publishing, and reproducible or independently attestable builds where supported.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.