CVE-2022-26078
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 · uneditedGallagher Controller 6000 is vulnerable to a Denial of Service attack via conflicting ARP packets with a duplicate IP address. This issue affects: Gallagher Gallagher Controller 6000 vCR8.60 versions prior to 220303a; vCR8.50 versions prior to 220303a; vCR8.40 versions prior to 220303a; vCR8.30 versions prior to 220303a.
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 · high confidenceThe Gallagher Controller 6000 contains a vulnerability in its ARP packet handling logic. An unauthenticated attacker on the local network can send conflicting ARP packets with duplicate IP addresses, causing the controller to become unresponsive and resulting in a denial of service. This is a network-layer attack exploiting the lack of proper ARP conflict validation in affected versions.
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>= 8.30, < 8.30.220303a>= 8.40, < 8.40.220303a>= 8.50, < 8.50.220303a>= 8.60, < 8.60.220303aCVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the device modelAccess the Gallagher Controller 6000 admin interface or check the physical device labeling to confirm the model is Gallagher Controller 6000Affected if The device is not a Gallagher Controller 6000, then it is not affected by this CVE
-
Determine the installed firmware versionLog into the controller admin panel or use the Gallagher command-line interface to view the firmware version. Typically found under System > About or using a 'show version' commandAffected if The installed firmware version falls within any of these ranges: >= 8.30 and < 8.30.220303a; >= 8.40 and < 8.40.220303a; >= 8.50 and < 8.50.220303a; >= 8.60 and < 8.60.220303a
-
Verify network accessibility to the controllerReview network configuration to determine if the Gallagher Controller 6000 is directly accessible from untrusted network segments. Check VLAN assignments and firewall rules controlling access to the deviceAffected if The controller is reachable from untrusted or unsegmented network segments where unauthenticated attackers could send ARP packets to the device
-
Check for ARP-related anomalies or device responsivenessMonitor network logs for duplicate ARP packet responses, or test device responsiveness by pinging the controller and observing if it becomes unresponsive after ARP activityAffected if The device shows signs of unresponsiveness when subjected to ARP packet conflicts, or network logs show duplicate ARP responses for the same IP address
A user is affected if they have a Gallagher Controller 6000 running firmware version 8.30 through 8.30.x (prior to 220303a), 8.40 through 8.40.x (prior to 220303a), 8.50 through 8.50.x (prior to 220303a), or 8.60 through 8.60.x (prior to 220303a), and the device is accessible from network segments where untrusted actors could send ARP packets.
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 · scoped8.30.220303a8.40.220303a8.50.220303a
Update Gallagher Controller 6000 to version 220303a or later for all affected branches (vCR8.30, vCR8.40, vCR8.50, vCR8.60). As a compensating control, implement network segmentation to restrict ARP packet traffic to trusted segments, and monitor for ARP anomalies.
Upgrade to firmware version 8.30.220303a, 8.40.220303a, 8.50.220303a, or 8.60.220303a (depending on your current branch)
- Identify the current firmware version of the Gallagher Controller 6000
- Determine which firmware branch (8.30, 8.40, 8.50, or 8.60) the controller is currently running
- Obtain the fixed firmware version 220303a for the appropriate branch from official Gallagher sources
- Follow Gallagher's standard firmware upgrade procedure to apply the update
- Verify the controller is running the patched version and network functionality is restored
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26078 — 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-2022-26078 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