CVE-2025-12602
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited/etc/avahi/services/z9.service can be Arbitrarily Written.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe BLU-IC2 and BLU-IC4 devices through version 1.19.5 contain an arbitrary file write vulnerability allowing attackers to write files to /etc/avahi/services/. This location stores Avahi service definition files (.service) which are parsed by the Avahi daemon, potentially enabling code execution through malicious service configurations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.20< 1.20CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelDetermine if the target device is a BLU-IC2 or BLU-IC4 unit from Azure Access product lineAffected if Device is a BLU-IC2 or BLU-IC4 model
-
Check firmware versionRetrieve the installed firmware version from the device system information or via device management interfaceAffected if Firmware version is 1.19.5 or lower, or any version prior to 1.20
-
Verify Avahi daemon is runningCheck if the Avahi service is active on the device and confirming it parses .service files from /etc/avahi/services/Affected if Avahi daemon is enabled and actively parsing service definition files
Environment is affected if it is a BLU-IC2 or BLU-IC4 device running firmware version 1.19.5 or lower (prior to 1.20) with the Avahi daemon enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.20
Upgrade BLU-IC2 and BLU-IC4 firmware to a version beyond 1.19.5. If no patched firmware is available, restrict write access to /etc/avahi/services/ and disable Avahi if not required.
Firmware 1.20
- Verify the current firmware version on the BLU-IC2 or BLU-IC4 device
- Download firmware version 1.20 or later from the vendor's official firmware distribution channel
- Follow the vendor's standard firmware update procedure for the specific device model
- After upgrade, verify that the device is running firmware version 1.20 or higher
- Confirm that the /etc/avahi/services/z9.service file is no longer arbitrarily writable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12602 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12602 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data