Summary
ZLT microservices-platform through version 6.0.0 may disable authorization checks when the zlt.security.auth.urlPermission.enable setting remains at its default value of false.
After authentication, users without assigned roles could access administrative APIs, including user management, role assignment, and Elasticsearch index operations.
Affected context
This vulnerability occurs in deployments of zlt2000 microservices-platform where URL-level permission enforcement is disabled by configuration. Authentication may still be required, but the platform can fail to verify whether the authenticated user has the roles or permissions needed for sensitive administrative endpoints.
Exploit preconditions
- Attack surface: Authenticated administrative and service APIs
- Required access: A valid user account or other means of passing authentication
- Trigger point: Requests to protected APIs while URL permission enforcement is disabled
- Why exploitation is possible: The application authenticates the user but does not consistently perform the subsequent authorization checks needed to validate roles and permissions
Why this happens
The underlying issue is a missing authorization control caused by a security-relevant permission-enforcement setting defaulting to disabled.
When authentication is treated as sufficient access control, the application may accept requests without evaluating the caller's roles against endpoint requirements. This behavior maps to CWE-862: Missing Authorization, in which a protected resource or operation lacks an effective permission check after identity verification.
Potential impact
- Unauthorized users may access administrative APIs
- Attackers could create, modify, or assign roles to accounts
- Sensitive user and permission data may be exposed or altered
- Elasticsearch indexes could be read, modified, or deleted
- The application environment may experience broader compromise or data integrity loss
General mitigation guidance
Mitigation generally focuses on making authorization enforcement secure by default and ensuring that every sensitive operation performs an explicit permission check.
Common defensive patterns include:
- Enable URL and method-level authorization by default
- Require explicit role or permission validation for administrative endpoints
- Use deny-by-default policies for unknown or unclassified routes
- Reduce reliance on client-supplied roles or claims without trusted verification
- Separate ordinary user capabilities from administrative and index-management privileges
- Apply least privilege to service accounts and Elasticsearch identities
- Treat security configuration as validated policy rather than optional application behavior
How teams detect issues like this
Organizations can identify this class of issue through:
- Configuration checks that flag disabled authorization enforcement
- Static analysis and code review for authenticated routes lacking role or permission checks
- API inventory reviews that classify administrative operations and verify protection coverage
- Integration tests using authenticated users with no roles or minimal privileges
- Policy enforcement that prevents insecure security defaults in deployment configuration
- Monitoring for administrative API access by accounts without corresponding privileges
Automated security review tools may help identify routes, configuration flags, and authorization middleware that are missing or bypassed.

