Summary
OpenReception's appointment platform allows unauthenticated requests to add attacker-controlled public keys to any tenant's staff encryption directory. Because those keys are later used to encrypt appointment data, an attacker may receive and decrypt future booking information and may also inject malformed entries that disrupt legitimate flows.
Affected context
The issue occurs in deployments of OpenReception before the security fix where the staff cryptographic-key registration route does not consistently enforce authentication or tenant and staff ownership. The risk is present when attacker-supplied key records are stored despite missing session or registration credentials, later exposed through the public booking flow, and included as encryption recipients for new appointments.
Exploit preconditions
- Attack surface: Network-accessible appointment and staff cryptographic-key API routes
- Required access: No authenticated account is required to submit the unauthorized key-registration request
- Trigger point: Processing a request to store a staff encryption key, followed by a booking flow that retrieves public keys
- Why exploitation is possible: Authorization checks only emit a warning or rely on flawed optional-field comparisons, while the database accepts arbitrary staff identifiers and duplicate active records
- Additional condition for confidentiality impact: A subsequent appointment must use the poisoned key directory for encryption
Why this happens
The primary defect is a missing authorization check, mapping to CWE-862: Missing Authorization. The handler continues with database insertion after detecting that the request lacks an authenticated session or valid registration context, so authentication and tenant or staff ownership are not enforced before a security-sensitive write.
The optional email field also permits an undefined-to-undefined comparison to satisfy the registration check, creating an alternate path that bypasses the expected warning. Weak validation of cryptographic fields, unrestricted staff identifiers, duplicate active rows, and the absence of uniqueness constraints further allow the unauthorized directory state to persist and affect downstream encryption decisions.
Potential impact
- An attacker may become an additional encryption recipient for future appointments
- Sensitive appointment payloads may be exposed to an unauthorized party
- Patient confidentiality and the platform's end-to-end encryption assurances may be undermined
- Malformed key records could disrupt legitimate appointment creation or retrieval
- Duplicate poisoned entries may increase operational and recovery complexity
- Security monitoring may miss some unauthorized attempts when the warning log is suppressed
General mitigation guidance
Mitigation generally centers on enforcing authorization before any cryptographic-directory mutation and ensuring that authorization is bound to the requested tenant and staff identity.
Common defensive patterns include:
- Rejecting requests unless a verified session or registration context is present
- Performing explicit tenant, staff, and invitation ownership checks before insertion
- Treating omitted optional fields as invalid when they participate in authorization decisions
- Validating public keys, key shares, identifiers, and related fields against strict format, length, and cryptographic constraints
- Enforcing database uniqueness and integrity constraints for active staff-key relationships
- Separating authentication failures from successful writes and generating consistent, tamper-resistant audit events
- Applying least privilege to service identities and limiting access to key-management data
- Designing downstream encryption flows to reject untrusted or unverifiable recipients by default
How teams detect issues like this
Detection can combine application, database, and code-level controls:
- Review routes that write tenant-scoped or staff-scoped security data for authorization checks that occur before persistence
- Use static analysis and code review rules to flag database inserts reached after warning-only authentication branches
- Test optional-field authorization logic, especially comparisons involving undefined, null, or empty values
- Monitor for key registrations without an authenticated principal, unknown staff identifiers, duplicate active records, and unusually high registration volume
- Alert on cryptographic records that fail format, length, or algorithm-specific validation
- Correlate key-directory changes with subsequent public booking-key retrieval and appointment creation
- Enforce CI policies requiring authorization, schema, and negative-path tests for sensitive API endpoints
- Use automated review tools as a supplementary way to identify missing authorization and insecure trust-boundary patterns

