Skip to main content
EPSS 0.7%top 48%

Git credentials are exposed in Atlantis logs (CVE-2024-52009)

0
High
Published: 11/08/2024 (11/08/2024, 19:03:35 UTC)
Source: GCVE Database
Product: github.com/runatlantis/atlantis

Description

Atlantis versions prior to 0.30.0 log GitHub tokens in plaintext during token rotation. This exposure in logs can allow unauthorized users with log access to impersonate the Atlantis application and perform privileged actions on GitHub organizations managed by Atlantis. The vulnerability was fixed in Atlantis v0.30.0.

CVSS v4.0

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
High
Subsq. Integrity
High
Subsq. Availability
High
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

Affected software

Goghsa
github.com/runatlantis/atlantis
Affected versions
<0.30.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 06/26/2026, 22:15:13 UTC

Technical Analysis

Atlantis, when used to manage GitHub organizations, logged sensitive GitHub tokens (starting with 'ghs_') in its debug logs during token rotation. These logs were accessible to users with read-only access to Argo CD, enabling them to obtain administration privileges on the GitHub organization and potentially escalate to cluster admin privileges on Kubernetes clusters managed via Infrastructure-as-Code. The issue was reported and fixed in pull request 4667, included in Atlantis v0.30.0. No official security advisory or CVE was initially published, but this vulnerability is tracked as CVE-2024-52009.

Potential Impact

Exposure of GitHub tokens in logs allows attackers with read access to logs to impersonate Atlantis and perform administrative actions on GitHub organizations. This compromises repository security and can lead to further privilege escalation in Kubernetes environments managed through Atlantis. The vulnerability affects users deploying Atlantis with GitHub integration and token rotation enabled.

Mitigation Recommendations

Upgrade Atlantis to version 0.30.0 or later, where the logging of GitHub tokens during rotation has been fixed. Avoid granting unnecessary log read access to users. Patch status is confirmed fixed in Atlantis v0.30.0.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-gppm-hq3p-h4rp
Osv Schema Version
1.4.0
Aliases
["CVE-2024-52009"]
Ecosystems
["Go"]
Database Specific Severity
HIGH
Cvss Version
4.0

Threat ID: 6a3ef78c27e9c79719ff48b1

Added to database: 06/26/2026, 22:05:00 UTC

Last enriched: 06/26/2026, 22:15:13 UTC

Last updated: 09/10/2026, 19:36:48 UTC

Views: 17

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses