Azure Access BLU-IC2/BLU-IC4 up to 1.19.5 status code
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.8 | $0-$5k | 0.00 |
Summary
A vulnerability identified as very 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 status code. This vulnerability is referenced as CVE-2025-12516. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in Azure Access BLU-IC2 and BLU-IC4 up to 1.19.5. It has been rated as very critical. This issue affects some unknown functionality. The manipulation with an unknown input leads to a status code vulnerability. Using CWE to declare the problem leads to CWE-394. The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Lack of Graceful Error Handling - HTTP 5xx ErrorThis issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5 .
The weakness was published 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-12516 since 10/30/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price 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.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: Status codeCWE: CWE-394 / CWE-393
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/30/2025 Advisory disclosed10/30/2025 CVE reserved
10/30/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-12516 (🔒)
GCVE (CVE): GCVE-0-2025-12516
GCVE (VulDB): GCVE-100-330605
Entry
Created: 10/30/2025 18:15Updated: 11/10/2025 18:34
Changes: 10/30/2025 18:15 (64), 11/10/2025 18:34 (9)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.