Summary
An insecure direct object reference in OpenSign's getcontact Parse cloud function may allow unauthenticated remote attackers to retrieve contact records by supplying object references. Because the function uses the master key without authentication or authorization checks, exposed records may include personally identifiable information.
Affected context
The issue occurs in OpenSign deployments where the getcontact Parse cloud function is reachable by external clients and processes contact-object requests without verifying the caller's identity or access to the requested record. The risk is greater when contact records contain sensitive personal data and object identifiers can be discovered or enumerated.
Exploit preconditions
- Attack surface: The externally reachable
getcontactParse cloud function - Required access: No authenticated account or prior authorization may be required
- Trigger point: A request for a contact object handled by the cloud function
- Why exploitation is possible: The function uses elevated master-key privileges and returns the requested object without checking whether the requester is authorized to access it
Why this happens
The vulnerability results from an object-level authorization failure. The cloud function accepts a client-controlled object reference and retrieves the corresponding contact record with master-key privileges, but does not enforce authentication, ownership, tenancy, or record-level access controls before returning the data. This behavior maps to CWE-639: Authorization Bypass Through User-Controlled Key, commonly known as insecure direct object reference.
Potential impact
- Attackers may enumerate contact records
- Personally identifiable information may be disclosed
- Privacy and regulatory obligations could be affected
- Contact data may be aggregated for profiling or targeted abuse
- Exposure of records may enable follow-on social engineering
General mitigation guidance
Mitigation typically focuses on enforcing authorization at the server-side object access boundary and reducing reliance on client-controlled identifiers.
Common defensive patterns include:
- Require authentication before exposing contact data
- Apply record-level authorization checks for every requested object
- Scope queries to the authenticated user, tenant, or permitted business relationship
- Avoid returning sensitive fields unless they are required for the specific operation
- Treat master-key access as a tightly controlled service capability rather than a substitute for authorization
- Use non-enumerable references where appropriate, while retaining server-side authorization as the primary control
- Log and rate-limit repeated object lookups to reduce enumeration risk
How teams detect issues like this
Organizations commonly detect IDOR risks through:
- Static analysis and code review rules for client-controlled identifiers passed directly into database lookups
- Review signals such as master-key or administrative database access in unauthenticated handlers
- Tests that request another user's or tenant's object and verify denial or filtered responses
- API gateway and application policies requiring authentication and authorization for sensitive data endpoints
- Monitoring for sequential, high-volume, or unusually broad contact-record requests
Automated security testing and code review tools can help identify missing object-level authorization checks, but should be supplemented with contextual access-control testing.

