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

> An attacker within Bluetooth range can use a hard-coded password to disable beacon notifications in the Chirp Access mobile application.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-v82h-9xhx-c8hg

## What is CVE-2024-2197?

CVE-2024-2197 is a low-severity vulnerability in Chirp Access, published on 19 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2024-2197?


## How do I fix CVE-2024-2197?

No fix has been published for CVE-2024-2197 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-2197 being exploited?

There is no known exploitation of CVE-2024-2197 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2197 and fix it if it is affected.

What it is: CVE-2024-2197 is a low-severity vulnerability in Chirp Access, published on 19 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2197 in the wild and no public exploit code.

Affected product: Chirp Access. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-2197/ (Markdown: https://insights.sbomify.com/CVE-2024-2197/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-2197
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-2197
- OSV: https://osv.dev/vulnerability/CVE-2024-2197

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-2197/
Summaries are generated and may contain mistakes; the official description above is the record.