Skip to main content

BLU-IC2/IC4 Firmware CVE-2025-12220

CRITICAL
2025-10-25 a0340c66-c385-4f8b-991b-3d05f6fd5220
10.0
CVSS 4.0 · Vendor: a0340c66-c385-4f8b-991b-3d05f6fd5220
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed device network service
  2. Exploit
    Identify outdated BusyBox 1.31.1 firmware
  3. Execution
    Exploit known BusyBox vulnerability
  4. Impact
    Disclose sensitive data or disrupt device

Vulnerability Assessment

Exploitation Conditions

Exploitation requires network reachability to a BLU-IC2 or BLU-IC4 device running vulnerable firmware (through 1.19.5), which embeds the outdated BusyBox 1.31.1 userland; the attacker must reach whatever network-facing service or applet exposes the underlying BusyBox weakness. The description does not name the specific vulnerable applet, protocol, or configuration, so the exact triggering service is unconfirmed. Practical limiting factors: these are specialized access-control/intercom appliances typically deployed on segmented internal or physical-security networks, which constrains internet-wide exposure; realistic risk therefore hinges on whether the affected device service is actually reachable from an attacker's network position. Per CVSS no authentication or user interaction is required (PR:N/UI:N).

Impact

Signals conflict sharply here. The supplied CVSS 4.0 base score is a maximal 10.0 (AV:N/AC:L/AT:N/PR:N/UI:N with full VC/VI/VA and subsequent-system SC/SI/SA all High), implying trivial remote unauthenticated compromise with cascading impact. However, EPSS is only 0.37% (29th percentile), there is no CISA KEV listing, and no public exploit is referenced - so there is no evidence of real-world exploitation despite the perfect score. The description is also an aggregate placeholder ('Busybox 1.31.1 - Multiple Known Vulnerabilities'), meaning the 10.0 appears to be an umbrella rating for an outdated bundled component rather than a single verified full-chain RCE; the only technique tag is 'Information Disclosure', which does not by itself justify VI:H/VA:H and especially the subsequent-system (SC/SI/SA:H) metrics - those appear inflated and should be verified with the vendor. CWE is N/A and no individual BusyBox CVE is enumerated, so the true impact is unconfirmed. Net: treat as a genuine patch-management concern (end-of-life/old BusyBox in access-control firmware) but not a confirmed widespread-exploitation emergency - the low EPSS and absence of KEV/POC argue against the 10.0 reflecting imminent mass exploitation. Prioritize based on network exposure of the devices rather than on the raw score alone.

Exploit ScenarioDerived

An attacker with network reachability to a BLU-IC2 or BLU-IC4 access-control device (firmware ≤1.19.5) identifies that it ships the outdated BusyBox 1.31.1 and targets one of the publicly documented BusyBox vulnerabilities in an exposed service or applet to disclose sensitive data or interfere with device operation. No CVE-specific proof-of-concept is referenced, though generic public exploit information for older BusyBox versions is widely available. Realistic reach depends on whether the device's affected service is exposed beyond an isolated physical-security network.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 18, 2026

Network-reachable BLU-IC2 and BLU-IC4 devices running firmware through 1.19.5 embed BusyBox 1.31.1 and are exposed to multiple known BusyBox weaknesses that can compromise confidentiality, integrity, and availability. The vendor's CVSS 4.0 score is 10.0, but our assessment is CVSS 3.1 AV:N/AC:H/PR:N/UI:N with high C/I/A impact because exploitation depends on reaching a specific network-facing BusyBox service or applet whose identity is not confirmed. EPSS is 0.37% (29th percentile) and no public exploit identified at time of analysis.

RemediationAI

Upgrade BLU-IC2 and BLU-IC4 devices to a fixed firmware release later than 1.19.5 as specified in the vendor advisory at https://azure-access.com/security-advisories; the provided data does not name an exact fixed version, so confirm the target release before deployment. Until patched, reduce network reachability to the appliances: place them behind firewalls or VPNs, permit only required management and intercom traffic, and block unnecessary ports or BusyBox applets. Trade-offs are that tighter segmentation may disrupt remote management or integrations, and disabling unused applets may affect expected device functions. Monitor access logs for anomalous connections to the devices' network-facing services.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

BusyBox is a compact multi-call userland that supplies Unix utilities and shell applets in embedded Linux firmware, and version 1.31.1 is an outdated release with multiple known weaknesses. The CPE entries cpe:2.3:o:azure-access:blu-ic2_firmware:*:*:*:*:*:*:*:* and cpe:2.3:o:azure-access:blu-ic4_firmware:*:*:*:*:*:*:*:* identify the affected firmware operating systems rather than a standalone BusyBox package. The root-cause class is not specified in the provided data (CWE N/A), and the advisory groups several BusyBox issues under one identifier. Both the vendor and our assessment use a network attack vector, but our CVSS 3.1 score applies AC:H because the attacker must actually reach the vulnerable BusyBox service or applet on access-control/intercom appliances that are often placed on segmented physical-security networks. Per CVSS, no authentication or user interaction is required.

Know when Busybox gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220) PRIMARY 10.0 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
vuln.today AI 8.1 HIGH

Network, unauthenticated per input; AC:H because the specific BusyBox weakness and triggering service are unspecified/aggregated; impacts kept High but scope Unchanged, as no cross-system scope change is evidenced.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (a0340c66-c385-4f8b-991b-3d05f6fd5220).

CVSS VectorVendor: a0340c66-c385-4f8b-991b-3d05f6fd5220

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

Busybox 1.31.1 - Multiple Known Vulnerabilities.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.

Executive ViewAI

Why It Matters

BLU-IC2 and BLU-IC4 devices running firmware through 1.19.5 carry a critical network-reachable BusyBox exposure that could affect device confidentiality, integrity, and availability; no public exploit has been identified at time of analysis. Because no vendor-released patch is currently identified, leadership should treat these devices as an unresolved operational risk until they are inventoried, segmented, and vendor mitigation guidance is applied. Any business or operational locations relying on these devices for network connectivity should be prioritized for exposure review and interim controls.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; isolate and segment affected BLU-IC2 and BLU-IC4 devices, restrict network access to required services, disable unnecessary BusyBox applets or services, monitor for anomalous activity, and apply vendor workarounds when available.

Threat Intelligence Overview

EPSS Score
0.4%
Top 71% exploitable
Prevalence
Low
niche physical access-control/intercom hardware from a single vendor
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +50
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Affected Products (CPE)CVE.org

cpe:2.3:o:azure-access:blu-ic2_firmware:*:*:*:*:*:*:*:*
cpe:2.3:o:azure-access:blu-ic4_firmware:*:*:*:*:*:*:*:*
CVE-2016-2148 CRITICAL POC
9.8 Feb 09

Heap-based buffer overflow in the DHCP client (udhcpc) in BusyBox before 1.25.0 allows remote attackers to have unspecif

CVE-2017-16544 HIGH POC
8.8 Nov 20

In the add_match function in libbb/lineedit.c in BusyBox through 1.27.2, the tab autocomplete feature of the shell, used

CVE-2016-2147 HIGH POC
7.5 Feb 09

Integer overflow in the DHCP client (udhcpc) in BusyBox before 1.25.0 allows remote attackers to cause a denial of servi

CVE-2022-28391 HIGH POC
8.8 Apr 03

BusyBox through 1.35.0 allows remote attackers to execute arbitrary code if netstat is used to print a DNS PTR record's

CVE-2025-60876 MEDIUM POC
6.5 Nov 10

BusyBox wget thru 1.3.7 accepted raw CR (0x0D)/LF (0x0A) and other C0 control bytes in the HTTP request-target (path/que

CVE-2022-30065 HIGH POC
7.8 May 18

A use-after-free in Busybox 1.35-x's awk applet leads to denial of service and possibly code execution when processing a

CVE-2019-5747 HIGH POC
7.5 Jan 09

An issue was discovered in BusyBox through 1.30.0. Rated high severity (CVSS 7.5), this vulnerability is remotely exploi

CVE-2013-1813 HIGH POC
7.2 Nov 23

util-linux/mdev.c in BusyBox before 1.21.0 uses 0777 permissions for parent directories when creating nested directories

CVE-2021-42377 CRITICAL
9.8 Nov 15

An attacker-controlled pointer free in Busybox's hush applet leads to denial of service and possible code execution when

CVE-2018-1000517 CRITICAL
9.8 Jun 26

BusyBox project BusyBox wget version prior to commit 8e2174e9bd836e53c8b9c6e00d1bc6e2a718686e contains a Buffer Overflow

CVE-2023-42366 MEDIUM POC
5.5 Nov 27

A heap-buffer-overflow was discovered in BusyBox v.1.36.1 in the next_token function at awk.c:1159. Rated medium severit

CVE-2017-15873 MEDIUM POC
5.5 Oct 24

The get_next_block function in archival/libarchive/decompress_bunzip2.c in BusyBox 1.27.2 has an Integer Overflow that m

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy