GHSA-xh7v-965r-23f7 — atlantis
HIGHGHSA-xh7v-965r-23f7 is a high-severity (CVSS 7.5) Information Exposure vulnerability in github.com/runatlantis/atlantis. No vendor fix is recorded yet; mitigation options are listed below.
Atlantis Exposes Service Version Publicly on /status API Endpoint
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for GHSA-xh7v-965r-23f7.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-xh7v-965r-23f7 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/runatlantis/atlantisReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/runatlantis/atlantis | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/runatlantis/atlantis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of github.com/runatlantis/atlantis has shipped for GHSA-xh7v-965r-23f7 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xh7v-965r-23f7 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-xh7v-965r-23f7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-xh7v-965r-23f7 in your dependencies?
O3 Security finds GHSA-xh7v-965r-23f7 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.