ghsa-xh7v-965r-23f7
Vulnerability from github
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
http://<atlantis-host>/statususing a tool likecurlor 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 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.
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/runatlantis/atlantis"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "0.35.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-58445"
],
"database_specific": {
"cwe_ids": [
"CWE-200"
],
"github_reviewed": true,
"github_reviewed_at": "2025-09-05T21:18:47Z",
"nvd_published_at": "2025-09-06T20:15:30Z",
"severity": "LOW"
},
"details": "### Summary\nAtlantis 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\u0027s security posture.\n\n### Details\nThe `/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.\n\nFor 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.\n\n### PoC\n1. Issue a GET request to `http://\u003catlantis-host\u003e/status` using a tool like `curl` or a web browser.\n2. Note that the API response includes detailed version and build information.\n3. Verify that no authentication is required to access the endpoint, leading to public exposure.\n4. Cross-reference the disclosed version with public vulnerability databases (e.g., [NVD](https://nvd.nist.gov)) for likely vulnerabilities.\n\n### Impact\nThe 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.\n\n### CVS Severity Assessment\nBased 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.",
"id": "GHSA-xh7v-965r-23f7",
"modified": "2025-09-13T03:03:00Z",
"published": "2025-09-05T21:18:47Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/runatlantis/atlantis/security/advisories/GHSA-xh7v-965r-23f7"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-58445"
},
{
"type": "PACKAGE",
"url": "https://github.com/runatlantis/atlantis"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U",
"type": "CVSS_V4"
}
],
"summary": "Atlantis Exposes Service Version Publicly on /status API Endpoint"
}
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.