Skip to main content
VulnerabilityPublished Updated

CVE-2025-12603: Azure Access Technology BLU-IC2 · Out-of-bounds Write

Affects Azure Access Technology BLU-IC2Source CVE Database V5

0

Not known to be exploited · CVSS 2.3 Low : upgrade to 1.19.6 when convenient.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.19.6
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Azure Access Technology BLU-IC2 to 1.19.6.

Affected software

ProductAffectedFixed in
Azure Access Technology BLU-IC2Affected
  • <1.19.6
Fixed in
  • 1.19.6

AI-suggested

  1. Monitor Azure Access Technology advisories for official patches addressing CVE-2025-12603 and apply them promptly upon release.
  2. Restrict file system permissions to ensure that only trusted system processes and administrators can modify /etc/timezone.
  3. Implement file integrity monitoring on critical configuration files like /etc/timezone to detect unauthorized changes quickly.
  4. Employ network segmentation and access controls to limit exposure of BLU-IC2 and BLU-IC4 devices to untrusted networks.
  5. Conduct regular audits of user privileges on affected systems to minimize the risk of low-privilege accounts exploiting this vulnerability.
  6. Use centralized logging and time synchronization services (e.g., NTP) to detect anomalies in system time settings.
  7. Prepare incident response plans that include scenarios involving system time manipulation to reduce impact if exploitation occurs.

Description

/etc/timezone can be Arbitrarily Written.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.

References

Community reviews

Loading reviews…