Chirp Access
Approved changes feed: RSS · Atom
cpe:2.3:a:chirp_systems:chirp_access:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Chirp Systems (2c9ace8e-2b01-5bba-a589-0c7d41aae8cb) |
|---|---|
| Product | Chirp Access (686208d3-bac9-545e-80f6-5924ea4cf05d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-2197 |
vulnerable | 2026-06-08 06:33:30.566344 |
Chirp Systems Chirp Access Use of Hard-coded Password
MEDIUM (4.3)
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.
Published: 2024-03-19T23:46:14.505Z
Updated: 2024-08-01T19:03:39.092Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.