Summary
A sensitive information exposure vulnerability in Suprema BioStar 2 and BioStar X can return Active Directory service account credentials in cleartext through a settings API endpoint. An attacker who can reach the endpoint and submit a crafted GET request may obtain credentials that could be reused to access directory services or other connected systems.
Affected context
The issue affects deployments of Suprema BioStar 2 and BioStar X in which the vulnerable ad-server settings endpoint is reachable and returns directory service account information without adequate protection. Risk depends on network exposure, authentication controls, endpoint authorization, and whether the returned credentials are valid and privileged.
Exploit preconditions
- Attack surface: The
/api/v2/setting/adserversettingHTTP API endpoint - Required access: Ability to reach the endpoint; the required authentication and authorization level depends on deployment configuration
- Trigger point: A crafted GET request to the Active Directory server settings endpoint
- Why exploitation is possible: The endpoint may disclose service account credentials in cleartext rather than withholding or securely handling sensitive values
Why this happens
The underlying bug is an information disclosure pattern in which a configuration API exposes authentication material in a readable response. This maps to CWE-319: Cleartext Transmission of Sensitive Information, because credentials are returned without sufficient confidentiality protection at the application or transport boundary. Exposing secrets through general-purpose settings responses also increases the chance that they will be logged, cached, intercepted, or accessed by unauthorized users.
Potential impact
- An attacker may obtain valid Active Directory service account credentials
- Stolen credentials could enable unauthorized directory access
- An attacker could impersonate the service account or access connected systems
- Exposed credentials may support lateral movement or persistence
- Credential disclosure could lead to monitoring, access-control, or biometric system compromise
General mitigation guidance
Mitigation generally focuses on preventing secrets from being returned through routine configuration endpoints and reducing the trust placed in exposed credentials.
Common defensive patterns include:
- Returning only non-sensitive configuration metadata and redacting or omitting stored credentials
- Protecting secret values with dedicated secret-management mechanisms rather than general settings storage
- Enforcing authentication, authorization, and least privilege for administrative API endpoints
- Applying encrypted transport and avoiding query or response handling that can expose secrets to logs or caches
- Rotating potentially exposed service credentials and limiting their directory permissions
- Separating service accounts by function and restricting their access to only required resources
How teams detect issues like this
Organizations can identify similar weaknesses through:
- Static and API security analysis for endpoints that serialize password, token, or credential fields
- Code review checks for administrative settings APIs returning stored secrets
- Testing authenticated and unauthenticated API responses for secret disclosure and excessive data exposure
- Log and proxy review for requests to the affected settings endpoint and responses containing account credentials
- Policy enforcement requiring secret redaction, encrypted transport, and least-privilege service accounts
Automated API security and code review tools may help detect sensitive-field exposure during development and testing.

