Chirp Systems Chirp Access Use of Hard-coded Password
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Chirp Systems | Chirp Access | unaffected |
|
No data.
No data.
No data available yet.
Vendor Solution
Update to v1.26.0
Vendor Workaround
For additional information, please see Chirp Systems statement here https://statement.chirpsystems.com/chirp-systems-icsa-24-067-01-response.html or contact RealPage (Chirp Systems' parent company) via their support page https://www.realpage.com/support/ .
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-27157 | 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. |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.283% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.
No data.