dbcve.org
Controller 6000 FirmwareOperating system · Gallagher

CVE-2023-24590

HIGH · 8.8 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to 8.60.231116a or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
A format string issue in the Controller 6000's optional diagnostic web interface can be used to write/read from memory, and in some instances crash the Controller 6000 leading to a Denial of Service. This issue affects: Gallagher Controller 6000 8.60 prior to vCR8.60.231116a (distributed in 8.60.2550 (MR7)), all versions of 8.50 and prior.

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

A format string vulnerability exists in the optional diagnostic web interface of Gallagher Controller 6000. This allows an attacker to read from and write to memory through unsanitized user input passed to printf-style functions, potentially leading to arbitrary code execution. In some cases, the vulnerability can crash the controller, causing a Denial of Service.

MitigationUpgrade Gallagher Controller 6000 to vCR8.60.231116a (distributed in 8.60.2550 MR7) or later. If upgrade is not immediately possible, disable the optional diagnostic web interface until the patch can be applied.

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 6000 FirmwareOperating system
Affected:<= 8.50>= 8.60, < 8.60.231116a

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify Controller firmware version
    Access the Gallagher Controller 6000 administrative interface or check the firmware version through the system management console. Navigate to the firmware or system information section to retrieve the current installed version number.
    Affected if The installed version is 8.50 or lower, OR version 8.60.x through 8.60.231116a (versions 8.60.0 through 8.60.231116a before the patch). Versions 8.60.231116a and later are NOT affected.
  2. Locate the diagnostic web interface
    Check the Controller configuration for the optional diagnostic web interface settings. This is typically found in the web server or diagnostic configuration section of the Controller admin panel.
    Affected if The diagnostic web interface exists as a configurable optional feature and must be present in the configuration.
  3. Verify diagnostic interface status
    Inspect whether the diagnostic web interface is enabled or accessible. This may be visible in the network services list, web service configuration, or diagnostic settings within the Controller admin interface.
    Affected if The diagnostic web interface is ENABLED or accessible. The vulnerability ONLY affects systems where this optional feature is turned on.
  4. Test interface accessibility
    Attempt to access the diagnostic web interface endpoint via HTTP/HTTPS from an authorized network location using a browser or curl command (e.g., /diagnostics or similar path).
    Affected if The diagnostic web interface responds and accepts user input. This confirms the vulnerable feature is active.

A system is affected only if both conditions are true: (1) the installed firmware version is within the vulnerable ranges (8.50 or lower, OR 8.60 through 8.60.231116a) AND (2) the optional diagnostic web interface is enabled/accessible.

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.60.231116a or later
Fixed in 8.60.231116a
Interim mitigation

Upgrade Gallagher Controller 6000 to vCR8.60.231116a (distributed in 8.60.2550 MR7) or later. If upgrade is not immediately possible, disable the optional diagnostic web interface until the patch can be applied.

Recommended fix High confidence

vCR8.60.231116a (distributed in 8.60.2550 MR7) or later

  1. Confirm current Controller 6000 firmware version by accessing the controller's administration interface
  2. Identify if the optional diagnostic web interface is enabled; if so, consider disabling it as a temporary mitigation
  3. Obtain the fixed firmware vCR8.60.231116a (also distributed as 8.60.2550 MR7) from official Gallagher distribution channels
  4. Follow Gallagher's standard firmware upgrade procedure for Controller 6000, ensuring stable power during the update process
  5. After upgrade, verify the diagnostic web interface functionality and confirm the vulnerability is resolved
  6. Test that the Controller 6000 operates normally post-upgrade
Caveat Ensure compatibility with any integrated systems before upgrading; follow standard backup and rollback procedures

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

Fix this in Controller 6000 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
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,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-24590 — 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-24590 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