Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. All versions of Atlantis publicly expose detailed version information through 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. This issue does not currently have a fix.
Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. All versions of Atlantis publicly expose detailed version information through 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. This issue does not currently have a fix.
Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. All versions of Atlantis publicly expose detailed version information through 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. This issue does not currently have a fix.
### 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](https://owasp.org/www-project-top-ten/) and recommendations discussed in NIST SP 800-53, advocate for restricting such potentially exploitable information.
### PoC
1. Issue a GET request to `http://<atlantis-host>/status` using a tool like `curl` or a web browser.
2. Note that the API response includes detailed version and build information.
3. Verify that no authentication is required to access the endpoint, leading to public exposure.
4. Cross-reference the disclosed version with public vulnerability databases (e.g., [NVD](https://nvd.nist.gov)) for likely vulnerabilities.
### Impact
The vulnerability falls under the category of information disclosure. Attackers could use the version details to scan public vulnerability repositories and tailor attacks based on known flaws in that particular version. This could potentially escalate into a broader compromise if the underlying software has exploitable vulnerabilities. Therefore, the affected parties include any users or administrators who rely on Atlantis, as well as the maintainers who are responsible for keeping the service secure.
### CVS Severity Assessment
Based on the current circumstances, this issue is assessed as **CVS Severity: LOW**. However, if the disclosed version is known to contain critical vulnerabilities, the severity rating could be re-evaluated to **Medium**. It is recommended to restrict this information to safeguarded internal channels to mitigate the risk of targeted attacks.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Sep 6, 2025, 7:47:33 PM
dateUpdated: Sep 8, 2025, 2:35:06 PM
1 related source bulletins · separate from aliases
openSUSE-SU-2025:15564-1: govulncheck-vulndb-0.0.20250917T170349-1.1 on GA media
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.