Azure Access BLU-IC2/BLU-IC4 up to 1.19.5 on-chip debug and test interface with improper access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Azure Access BLU-IC2 and BLU-IC4 up to 1.19.5. Affected by this vulnerability is an unknown functionality. The manipulation leads to on-chip debug and test interface with improper access control. This vulnerability is documented as CVE-2025-12114. The attack needs to be performed locally. There is not any exploit available.
Details
A vulnerability, which was classified as critical, has been found in Azure Access BLU-IC2 and BLU-IC4 up to 1.19.5. This issue affects some unknown functionality. The manipulation with an unknown input leads to a on-chip debug and test interface with improper access control vulnerability. Using CWE to declare the problem leads to CWE-1191. The chip does not implement or does not correctly perform access control to check whether users are authorized to access internal registers and test modes through the physical debug/test interface. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Enabled serial console could potentially leak information that might help attacker to find vulnerabilities.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.
The weakness was released by Kevin Schaller, Benjamin Lafois, Alexi Bitsios, Sebastian Toscano and Dominik Schneider. The advisory is shared at azure-access.com. The identification of this vulnerability is CVE-2025-12114 since 10/23/2025. The exploitation is known to be difficult. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 7.0
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: On-chip debug and test interface with improper access controlCWE: CWE-1191
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/23/2025 Advisory disclosed10/23/2025 CVE reserved
10/23/2025 VulDB entry created
11/10/2025 VulDB entry last update
Sources
Advisory: azure-access.comResearcher: Kevin Schaller, Benjamin Lafois, Alexi Bitsios, Sebastian Toscano, Dominik Schneider
Status: Confirmed
CVE: CVE-2025-12114 (🔒)
GCVE (CVE): GCVE-0-2025-12114
GCVE (VulDB): GCVE-100-329681
Entry
Created: 10/23/2025 18:14Updated: 11/10/2025 16:26
Changes: 10/23/2025 18:14 (64), 11/10/2025 16:26 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.