CVE-2024-2197

Beacon notification disruption via hard-coded password

Published Mar 19, 2024 · Updated Aug 1, 2024

Hard-coded credentials in Chirp Systems Chirp Access before 1.26.0 allow physically proximate attackers to alter Bluetooth beacon settings. The app embeds BEACON_PASSWORD and accepts that shared secret when authorizing changes to beacon configuration. Bluetooth proximity and access to a compatible beacon are required; the change can stop nearby-entry notifications but cannot reconfigure readers or locksets or prevent authorized locking and unlocking.

CVSS severity2.3
Low
EPSS probability0.28%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Hard-coded credentials in Chirp Systems Chirp Access before 1.26.0 allow physically proximate attackers to alter Bluetooth beacon settings. The app embeds BEACON_PASSWORD and accepts that shared secret when authorizing changes to beacon configuration. Bluetooth proximity and access to a compatible beacon are required; the change can stop nearby-entry notifications but cannot reconfigure readers or locksets or prevent authorized locking and unlocking.

The record

CVE
CVE-2024-2197
Published
Mar 19, 2024
Updated
Aug 1, 2024
Vendor
Chirp Systems
Product
Chirp Access
Classifications
CWE-259, T1552.001
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Mar 19, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 1, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <v1.26.0

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Chirp Systems · Chirp Accessversion=0 <v1.26.0

Published CVSS scores

2.3ICS-CERTCVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
4.3ICS-CERTCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-259Use of Hard-coded Password
T1552.001Unsecured Credentials: Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo