# CVE-2024-52009: Git credentials are exposed in atlantis logs

> Attackers with log access can steal GitHub credentials, enabling impersonation and potential organization administration privileges.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Nov 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-gppm-hq3p-h4rp, GO-2024-3265

## What is CVE-2024-52009?

CVE-2024-52009 is a high-severity vulnerability in runatlantis atlantis, published on 8 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2024-52009?

3 open source packages ship an affected version, including github.com/runatlantis/atlantis. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/runatlantis/atlantis` | Go | All versions | 0.30.0 |
| `github.com/runatlantis/atlantis` | Go | All versions | 0.30.0 |
| `github.com/runatlantis/atlantis` | Go | All versions | 0.30.0 |

Products: Runatlantis Atlantis.

## How do I fix CVE-2024-52009?

Upgrade github.com/runatlantis/atlantis to 0.30.0 or later.

## Is CVE-2024-52009 being exploited?

There is no known exploitation of CVE-2024-52009 in the wild and no public exploit code.

## Other vulnerabilities in runatlantis atlantis

- [CVE-2022-24912](https://insights.sbomify.com/CVE-2022-24912/): Timing Attack (high 7.5)
- [CVE-2025-58445](https://insights.sbomify.com/CVE-2025-58445/): Atlantis Exposes Service Version Publicly on /status API Endpoint (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52009 and fix it if it is affected.

What it is: CVE-2024-52009 is a high-severity vulnerability in runatlantis atlantis, published on 8 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52009 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/runatlantis/atlantis (Go): affected all versions; fixed in 0.30.0
- github.com/runatlantis/atlantis (Go): affected all versions; fixed in 0.30.0
- github.com/runatlantis/atlantis (Go): affected all versions; fixed in 0.30.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-52009/ (Markdown: https://insights.sbomify.com/CVE-2024-52009/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-52009
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-52009
- OSV: https://osv.dev/vulnerability/CVE-2024-52009

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-52009/
Summaries are generated and may contain mistakes; the official description above is the record.