Azure Access BLU-IC2/BLU-IC4 up to 1.19.5 vulnerable third-party component
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Azure Access BLU-IC2 and BLU-IC4 up to 1.19.5. It has been classified as very critical. This affects an unknown function. This manipulation causes vulnerable third-party component. This vulnerability is tracked as CVE-2025-12219. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as very critical was found in Azure Access BLU-IC2 and BLU-IC4 up to 1.19.5. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a vulnerable third-party component vulnerability. The CWE definition for the vulnerability is CWE-1395. The product has a dependency on a third-party component that contains one or more known vulnerabilities. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Vulnerable Components in Azure Access OS.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.
The weakness was disclosed by Kevin Schaller, Benjamin Lafois, Alexi Bitsios, Sebastian Toscano and Dominik Schneider. It is possible to read the advisory at azure-access.com. This vulnerability is known as CVE-2025-12219 since 10/25/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/10/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-35933). Be aware that VulDB is the high quality source for 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: 9.8VulDB Meta Temp Score: 9.8
VulDB Base Score: 9.8
VulDB Temp Score: 9.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Vulnerable third-party componentCWE: CWE-1395
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
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/25/2025 Advisory disclosed10/25/2025 CVE reserved
10/25/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-12219 (🔒)
GCVE (CVE): GCVE-0-2025-12219
GCVE (VulDB): GCVE-100-329887
EUVD: 🔒
Entry
Created: 10/25/2025 18:19Updated: 11/10/2025 17:15
Changes: 10/25/2025 18:19 (64), 10/25/2025 19:42 (1), 11/10/2025 17:15 (9)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.