OpenReception: unauthenticated ML-KEM key injection into the staff-crypto recipient directory in any tenant
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenReception's appointment booking platform, which uses end-to-end encryption for patient data, is affected. An unauthenticated remote attacker can register their own encryption key in any tenant's staff recipient directory, so future appointment data in that tenant gets encrypted to the attacker as well as to legitimate staff, exposing patient information.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
OpenReception's appointment booking software provides an end-to-end encrypted appointment booking platform. In versions 2.1.0 and prior, an unauthenticated attacker can store an arbitrary ML-KEM-768 public key under any existing user's identity in any tenant's staff-crypto recipient directory. The product's design guarantees that appointment data is end-to-end encrypted to staff members and that the staff recipient directory is not attacker-writable, so that even administrators and the operator cannot read patient data. This endpoint breaks that guarantee for an unauthenticated remote actor: it allows writing an arbitrary encryption recipient into the recipient directory of any tenant. The injected key receives the tunnel key of every appointment booked afterward in that tenant, because booking clients encrypt to all active staff keys. The attacker holds the corresponding secret key and is a persistent, unauthorized recipient of that key material. At time of publication, there are no publicly available patches.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- open-reception appointment-booking-software
through 2.1.0