Summary Atlantis publicly exposes detailed version information on its /status endpoint. This information disclosure could allow attackers to identify and target known vulnerabilities associated with the specific versions, potentially compromising the service's security posture. Details The /status endpoint in Atlantis returns not only a health check but also detailed version and build information. This disclosure violates the principle of minimizing exposed sensitive metadata and can be leveraged by adversaries to correlate the version information with public vulnerability databases, including CVE listings. Although Atlantis is a public repository maintained by an external team, reducing this exposure can lessen the overall risk of targeted attacks. For example, the source code handling the /status endpoint exposes version details that allow one to infer software dependencies and system configurations. Best practices, including guidelines from the OWASP Top 10 and recommendations discussed in NIST SP 800-53, advocate for restricting such potentially exploitable information. PoC Issue a GET request to https://<atlantis-host>/status using a tool like curl or a web browser. Note that the API response includes detailed version and build information. Verify that no authentication is required to access the endpoint, leading to public exposure. Cross-reference the disclosed version with public vulnerability databases (e.g., NVD) for likely vulnerabilities. Impact The…Read More