dbcve.org
Acs100 FirmwareOperating system · Brivo

CVE-2023-6260

HIGH · 8.8 CVSS v3.1 Published 2024-02-19
Fix available
A fix is available. Upgrade to 6.2.4.3 or later.
See remediation →
93/100
Remediation priority · Urgent
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
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability in Brivo ACS100, ACS300 allows OS Command Injection, Bypassing Physical Security.This issue affects ACS100 (Network Adjacent Access), ACS300 (Physical Access): from 5.2.4 before 6.2.4.3.

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

OS Command Injection vulnerability in Brivo ACS100 and ACS300 physical access control panels allows remote attackers to execute arbitrary OS commands by injecting special elements into input fields. The ACS100 is exploitable via network-adjacent access while ACS300 requires physical access. Successful exploitation enables attackers to bypass physical security controls entirely.

MitigationUpgrade Brivo ACS100/ACS300 firmware to version 6.2.4.3 or later to patch the command injection vulnerability. Network segmentation and restricting administrative access should be implemented as compensating controls until patching is complete.

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
Acs100 FirmwareOperating system
Affected:>= 5.2.4, <= 6.2.4.3
Acs300 FirmwareOperating system
Affected:>= 5.2.4, < 6.2.4.3

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

CVSS:3.1/AV:A/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. Identify the Brivo device model
    Access the device administrative interface or check physical device labeling to confirm whether the hardware is an ACS100 or ACS300 panel
    Affected if Device is a Brivo ACS100 or ACS300 panel
  2. Determine the installed firmware version
    Log into the Brivo ACS administrative console and navigate to System > Firmware or About section to view the current firmware version number
    Affected if Firmware version is 5.2.4 or higher (for either model)
  3. Compare ACS100 version against affected range
    For ACS100 units, verify if the firmware version falls between 5.2.4 and 6.2.4.3 inclusive
    Affected if ACS100 firmware version >= 5.2.4 AND <= 6.2.4.3
  4. Compare ACS300 version against affected range
    For ACS300 units, verify if the firmware version is 5.2.4 or higher but below 6.2.4.3
    Affected if ACS300 firmware version >= 5.2.4 AND < 6.2.4.3
  5. Assess network exposure for ACS100
    Review network configuration to determine if the ACS100 panel administrative interface is accessible from network-adjacent positions (not isolated behind strict access controls)
    Affected if ACS100 firmware is in the affected range AND the device is network-adjacent accessible

You are affected if you have a Brivo ACS100 panel running firmware 5.2.4 through 6.2.4.3 (network-adjacent exploitable) or an ACS300 panel running firmware 5.2.4 through 6.2.4.2 (requires 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 6.2.4.3 or later
Fixed in 6.2.4.3
Interim mitigation

Upgrade Brivo ACS100/ACS300 firmware to version 6.2.4.3 or later to patch the command injection vulnerability. Network segmentation and restricting administrative access should be implemented as compensating controls until patching is complete.

Recommended fix High confidence

Firmware version 6.2.4.3 or later

  1. Verify current firmware version on the ACS100 or ACS300 device via the admin interface or CLI
  2. Download firmware version 6.2.4.3 or later from the official Brivo support portal (support.brivo.com)
  3. Review Brivo upgrade documentation and ensure proper backup of system configuration
  4. Upload the new firmware file through the device's web interface or appropriate provisioning method
  5. Verify the upgrade was successful and confirm the device is running firmware >= 6.2.4.3
  6. Test that physical access control functionality remains operational post-upgrade
Caveat Review Brivo release notes for any functional changes or configuration adjustments required between your current version and 6.2.4.3; ensure compatibility with connected systems before upgrading

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

Fix this in Acs100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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