Summary
disconf 2.6.36 exposes several configuration-fetching APIs without authentication because they are explicitly whitelisted by the login interceptor. An anonymous attacker may read configuration items and files managed by the configuration center, potentially revealing secrets and sensitive operational data.
Affected context
The vulnerability occurs in disconf deployments where the following configuration-fetching routes remain reachable without an authenticated session:
/api/config/item/api/config/file/api/config/list/api/config/simple/list
Risk depends on network exposure and on whether the configuration center contains credentials, tokens, internal service details, or other sensitive values.
Exploit preconditions
- Attack surface: HTTP configuration-management APIs
- Required access: Network connectivity to the disconf service; no valid account may be required
- Trigger point: Requests to the exposed configuration-fetching endpoints
- Why exploitation is possible: The login interceptor explicitly permits these paths, allowing requests to proceed without authentication or authorization checks
Why this happens
The underlying flaw is an authorization design error in which sensitive data-fetching endpoints are treated as publicly accessible by an authentication bypass or whitelist rule. This maps to CWE-284: Improper Access Control, because the application does not consistently enforce the required security policy before returning managed configuration data. The insecure pattern is allowing route-level exceptions to override the protection expected for sensitive resources.
Potential impact
- Attackers may retrieve configuration items and files without authentication
- Exposed credentials or tokens could enable access to connected services
- Internal endpoints, infrastructure details, and deployment settings could be disclosed
- The leaked information could support follow-on attacks, lateral movement, or data tampering
- Organizations may experience confidentiality, integrity, or availability impacts if disclosed secrets are reused
General mitigation guidance
Mitigation generally focuses on making authentication and authorization mandatory for sensitive configuration APIs.
Common defensive patterns include:
- Removing public route exceptions for configuration-fetching endpoints
- Enforcing authentication and resource-level authorization before returning configuration data
- Applying least-privilege access so users and services receive only the configuration they require
- Reducing sensitive values stored in centralized configuration where practical
- Separating secrets from ordinary configuration and using dedicated secret-management controls
- Applying network segmentation, gateway policy, and deny-by-default access controls
- Avoiding detailed configuration responses when a caller does not need the complete value
How teams detect issues like this
Organizations can identify similar issues through:
- Static analysis and route audits that flag sensitive endpoints excluded from authentication middleware
- Code review checks for permissive interceptor, filter, gateway, or allowlist rules
- Integration tests that verify anonymous requests receive denial responses for every configuration API
- API inventory reviews comparing sensitive resources with enforced authentication and authorization policies
- Web application monitoring for unauthenticated requests and unusual bulk reads of configuration endpoints
- Automated security testing and policy checks in CI pipelines to detect access-control regressions

