CVE-2024-52009
Runatlantis Atlantis information disclosure
- Published8 Nov 2024
Description
Atlantis is a self-hosted golang application that listens for Terraform pull request events via webhooks. Atlantis logs contains GitHub credentials (tokens `ghs_...`) when they are rotated. This enables an attacker able to read these logs to impersonate Atlantis application and to perform actions on GitHub. When Atlantis is used to administer a GitHub organization, this enables getting administration privileges on the organization. This was reported in #4060 and fixed in #4667 . The fix was included in Atlantis v0.30.0. All users are advised to upgrade. There are no known workarounds for this vulnerability.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://argo-cd.readthedocs.io/en/stable/operator-manual/security
- https://github.com/runatlantis/atlantis/issues/4060
- https://github.com/runatlantis/atlantis/pull/4667
- https://github.com/runatlantis/atlantis/releases/tag/v0.30.0
- https://github.com/runatlantis/atlantis/security/advisories/GHSA-gppm-hq3p-h4rp
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2024-52009 being actively exploited?
CVE-2024-52009 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.72%.
How severe is CVE-2024-52009?
CVE-2024-52009 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.72% probability of exploitation.
Which products are affected by CVE-2024-52009?
Affected products include Runatlantis Atlantis.
How do I fix CVE-2024-52009?
Upgrade affected software to a fixed version, for example Runatlantis Atlantis 0.30.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2024-52009 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.