dbcve.org
Access Control System FirmwareOperating system · Kastle

CVE-2024-45861

HIGH · 7.5 CVSS v3.1 Published 2024-09-19
Fix available
A fix is available. Upgrade to 2024-05-01 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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
Kastle Systems firmware prior to May 1, 2024, contained a hard-coded credential, which if accessed may allow an attacker to access sensitive information.

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 confidence

Kastle Systems access control firmware versions released prior to May 1, 2024, contain a hardcoded credential embedded in the firmware image. An attacker who obtains this credential through reverse engineering, documentation leak, or other means can authenticate to affected devices and access sensitive building security data.

MitigationUpdate all Kastle Systems firmware to versions released on or after May 1, 2024, which contain the patched firmware without the hardcoded credential. Coordinate with Kastle Systems support for device-specific update procedures.

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
Access Control System FirmwareOperating system
Affected:< 2024-05-01

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 device as a Kastle Systems access control system
    Locate the physical device or check network inventory for Kastle Systems access control hardware. Look for Kastle branding, model numbers, or check device documentation/management interface for the manufacturer field.
    Affected if The device is not manufactured by Kastle Systems, then it is not affected by this specific CVE.
  2. Determine the installed firmware version
    Access the Kastle device management interface, web console, or use the vendor-provided management software to view the current firmware version. Check device status pages, about screens, or firmware information menus.
    Affected if Unable to retrieve firmware version information from the device.
  3. Check the firmware release date
    Compare the installed firmware version or build date against the cutoff date of May 1, 2024. Note that some systems display version numbers while others display dates - consult Kastle documentation if version-to-date mapping is needed.
    Affected if The firmware was released prior to May 1, 2024, indicating the device contains the hardcoded credential.
  4. Verify the device is running Kastle Access Control System Firmware specifically
    Confirm through the device management interface, system information page, or management software that the installed firmware is Kastle Access Control System Firmware and not a different Kastle product line.
    Affected if The device runs a different Kastle product or non-Kastle firmware, it falls outside this specific CVE scope.

A user is affected if their Kastle Access Control System device runs firmware released before May 1, 2024, as this version range contains the hardcoded credential vulnerability.

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 2024-05-01 or later
Fixed in 2024-05-01
Interim mitigation

Update all Kastle Systems firmware to versions released on or after May 1, 2024, which contain the patched firmware without the hardcoded credential. Coordinate with Kastle Systems support for device-specific update procedures.

Recommended fix Moderate confidence

Access Control System Firmware >= 2024-05-01 (contact Kastle Systems for exact version number)

  1. Contact Kastle Systems directly to obtain the fixed firmware version released on or after May 1, 2024
  2. Request the specific firmware update from Kastle Systems technical support
  3. Follow Kastle Systems' official firmware update procedure to apply the patched firmware
  4. After upgrading, change any default credentials and review access controls

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

Fix this in Access Control System Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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