dbcve.org
Ilx 507 FirmwareOperating system · Alpsalpine

CVE-2025-8475

HIGH · 7.4 CVSS v3.0 Published 2025-08-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated

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
Alpine iLX-507 AVRCP Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Alpine iLX-507 devices. User interaction is required to exploit this vulnerability in that the target must connect to a malicious Bluetooth device. The specific flaw exists within the implementation of the AVRCP protocol. 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 root. Was ZDI-CAN-26321.

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 · high confidence

Stack-based buffer overflow in Alpine iLX-507 AVRCP protocol implementation allows network-adjacent attackers to execute arbitrary code via malicious Bluetooth device connection. The vulnerability stems from insufficient validation of user-supplied data length before copying to a fixed-length stack buffer, enabling root-level code execution.

MitigationLimit Bluetooth device pairing to trusted devices only and await official firmware update from Alpine. Network segmentation and Bluetooth disable when not in use can reduce exposure.

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
Ilx 507 FirmwareOperating system
Affected:= 6.0.000

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
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:L/PR:L/UI:R/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 device model
    Locate the model number on the Alpine iLX-507 unit (typically on the front panel, back, or in system settings under 'Device Information' or 'About')
    Affected if Device is not an Alpine iLX-507 unit, then not affected by this specific CVE
  2. Check firmware version
    Access the unit's settings menu, navigate to 'System' or 'Information' section, and locate the firmware version entry. On Alpine iLX-507, this is typically found under Settings > System Information > Firmware Version
    Affected if Firmware version is 6.0.000 exactly, then this specific version is affected by the buffer overflow
  3. Verify Bluetooth is enabled
    Check the unit's Bluetooth status in Settings > Bluetooth. Confirm whether the Bluetooth radio is turned ON
    Affected if Bluetooth is disabled, the attack surface is not exposed as the vulnerability requires a Bluetooth connection
  4. Confirm AVRCP functionality is active
    Check Bluetooth settings for AVRCP (Audio/Video Remote Control Profile) status. This may be visible under paired device details or as 'AVRCP' toggle in Bluetooth audio settings
    Affected if AVRCP is not configured or no Bluetooth audio devices are paired, the vulnerable code path may not be exercised

Affected if the device is an Alpine iLX-507 running firmware version 6.0.000 with Bluetooth and AVRCP enabled, allowing untrusted Bluetooth device pairing that could trigger the stack buffer overflow in the AVRCP protocol handler.

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

Limit Bluetooth device pairing to trusted devices only and await official firmware update from Alpine. Network segmentation and Bluetooth disable when not in use can reduce exposure.

Fix this in Ilx 507 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8475 — 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-2025-8475 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