dbcve.org
Controller 7000 FirmwareOperating system · Gallagher

CVE-2023-6355

MEDIUM · 6.8 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to 8.70.231204a / 8.80.231204a or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

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
Incorrect selection of fuse values in the Controller 7000 platform allows an attacker to bypass some protection mechanisms to enable local debug. This issue affects: Gallagher Controller 7000 9.00 prior to vCR9.00.231204b (distributed in 9.00.1507 (MR1)), 8.90 prior to vCR8.90.231204a (distributed in 8.90.1620 (MR2)), 8.80 prior to vCR8.80.231204a (distributed in 8.80.1369 (MR3)), 8.70 prior to vCR8.70.231204a (distributed in 8.70.2375 (MR5)).

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 confidence

The Controller 7000 platform has incorrectly configured fuse values in its hardware security implementation. These fuses are meant to protect sensitive debug interfaces from being accessed. Due to the incorrect selection, an attacker with local physical access can bypass certain protection mechanisms and enable local debugging capabilities, potentially exposing sensitive system functions.

MitigationUpgrade the Gallagher Controller 7000 firmware to the specified patched versions: vCR9.00.231204b (9.00.1507 MR1), vCR8.90.231204a (8.90.1620 MR2), vCR8.80.231204a (8.80.1369 MR3), or vCR8.70.231204a (8.70.2375 MR5) depending on the currently deployed release line.

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
Controller 7000 FirmwareOperating system
Affected:>= 8.70, < 8.70.231204a>= 8.80, < 8.80.231204a>= 8.90, < 8.90.231204a>= 9.00, < 9.00.231204b

CVSS 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
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Retrieve installed firmware version
    Access the Gallagher Controller 7000 management interface, CLI, or system information page to identify the currently running firmware version
    Affected if The firmware version is 8.70.x and below 8.70.231204a, OR 8.80.x and below 8.80.231204a, OR 8.90.x and below 8.90.231204a, OR 9.00.x and below 9.00.231204b

The controller is vulnerable if its firmware version is within any of the affected ranges, meaning it has the incorrectly configured hardware security fuses that could allow debug interface access with physical access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.70.231204a / 8.80.231204a / 8.90.231204a or later
Fixed in 8.70.231204a8.80.231204a8.90.231204a
Interim mitigation

Upgrade the Gallagher Controller 7000 firmware to the specified patched versions: vCR9.00.231204b (9.00.1507 MR1), vCR8.90.231204a (8.90.1620 MR2), vCR8.80.231204a (8.80.1369 MR3), or vCR8.70.231204a (8.70.2375 MR5) depending on the currently deployed release line.

Recommended fix High confidence

Upgrade to vCR8.70.231204a, vCR8.80.231204a, vCR8.90.231204a, or vCR9.00.231204b (depending on your current version branch)

  1. Identify the current firmware version of the Controller 7000 by accessing the controller's web interface or command-line interface
  2. Determine which version branch is currently running (8.70, 8.80, 8.90, or 9.00)
  3. Download the appropriate fixed firmware version from security.gallagher.com or the official Gallagher support portal: vCR8.70.231204a for 8.70 branch, vCR8.80.231204a for 8.80 branch, vCR8.90.231204a for 8.90 branch, or vCR9.00.231204b for 9.00 branch
  4. Review Gallagher upgrade documentation and ensure proper backup of configuration settings
  5. Initiate firmware upgrade through the controller's management interface, following the manufacturer's recommended upgrade procedure
  6. Verify the upgrade was successful by checking the new firmware version
  7. Confirm that the local debug protection mechanisms are now properly enforced
Caveat Review Gallagher release notes for your specific version branch to check for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Controller 7000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6355 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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