Summary
Jet Admin contains an authorization flaw that may let an attacker connect a malicious app to another user's custom domain and alter its authentication configuration. If the target uses an OAuth provider, the attack may also expose the victim workspace's OAuth Client ID and Client Secret to the attacker.
Affected context
The vulnerability occurs in Jet Admin deployments that support custom domains, user-created applications, and configurable authentication providers. Risk increases when domain-connection and authentication-management actions are not consistently scoped to the owning workspace, allowing a user-controlled application or configuration to be associated with another user's domain.
Exploit preconditions
- Attack surface: Custom-domain management, application creation, and authentication configuration interfaces
- Required access: An authenticated Jet Admin account with the ability to create an application or manage a domain connection
- Target condition: A victim custom domain and, potentially, an OAuth provider configured in the victim workspace
- Trigger point: Associating an attacker-controlled app with the target domain and changing its authentication settings
- Why exploitation is possible: Authorization checks may fail to verify ownership and workspace boundaries for domain and authentication operations
Why this happens
The underlying issue is improper authorization enforcement, mapped to CWE-862: Missing Authorization. The application appears to permit sensitive domain and authentication operations without reliably confirming that the requesting user has authority over the target workspace, domain, and associated credentials. This insecure pattern can allow cross-tenant resource reassignment and unintended disclosure of authentication configuration data.
Potential impact
- An attacker could reroute traffic for a victim's custom domain to an attacker-controlled application
- Users visiting the affected domain may be directed to attacker-controlled content
- OAuth Client IDs and Client Secrets could be exposed to an unauthorized workspace
- The attacker could potentially impersonate trusted application behavior or intercept authentication flows
- The incident could cause phishing, data exposure, or broader tenant compromise depending on downstream permissions
General mitigation guidance
Mitigation typically focuses on enforcing consistent, server-side authorization at every domain and authentication-management operation.
Common defensive patterns include:
- Verify ownership and workspace membership before allowing domain association or authentication changes
- Enforce tenant isolation for applications, domains, and credential records
- Apply least-privilege access to OAuth configuration and prevent secrets from being copied across workspaces
- Require reauthentication or step-up approval for high-impact domain and identity-provider changes
- Use secure-by-default domain binding, including explicit ownership verification and controlled reassignment workflows
- Rotate potentially exposed OAuth secrets and review existing domain, application, and authentication configuration relationships
How teams detect issues like this
Organizations commonly detect authorization gaps through:
- Static and dynamic analysis of domain, workspace, and authentication-management endpoints
- Code review checks for object-level authorization performed only in client-side logic or at route level
- Tests that attempt cross-workspace resource references and unauthorized domain reassignment
- Audit policies for changes to custom domains, OAuth settings, client credentials, and application ownership
- Alerts for unexpected domain-to-application changes, authentication-provider modifications, or credential access
Automated application-security testing and policy checks can help identify missing ownership validation before deployment.

