Is CVE-2024-52009 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2024-52009 being exploited in the wild.

How severe is CVE-2024-52009?

High severity, with a CVSS score of 4, published 8 November 2024.

Which products and versions are affected?

Atlantis < 0.30.0; github.com/runatlantis/atlantis (Go) < 0.30.0, SEMVER:introduced=0,fixed=0.30.0.

Is there a fix for CVE-2024-52009?

Yes. github.com/runatlantis/atlantis (Go): upgrade to 0.30.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2024-52009 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2024-52009?

Check whether you run Atlantis or github.com/runatlantis/atlantis (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2024-52009: runatlantis Atlantis sensitive information leak in logs

Q: Which products and versions are affected?

Atlantis < 0.30.0; github.com/runatlantis/atlantis (Go) < 0.30.0, SEMVER:introduced=0,fixed=0.30.0.

Q: Is there a fix for CVE-2024-52009?

Yes. github.com/runatlantis/atlantis (Go): upgrade to 0.30.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2024-52009 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2024-52009?

Check whether you run Atlantis or github.com/runatlantis/atlantis (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2024-52009 · Severity: high · CVSS 4 · Published 2024-11-08

Atlantis, a tool used for automating Terraform workflows, was found to leak sensitive GitHub credentials in its application logs during token rotation. An attacker or unauthorized employee with access to these logs could steal these credentials to impersonate the application and gain administrative control over GitHub organizations and repositories. This could lead to unauthorized infrastructure changes or full compromise of source code and deployment environments.

Technologies: Atlantis, github.com/runatlantis/atlantis (Go). Vendors: Atlantis, Go.

Quick answers

Is CVE-2024-52009 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2024-52009 being exploited in the wild.
How severe is CVE-2024-52009?: High severity, with a CVSS score of 4, published 8 November 2024.
Which products and versions are affected?: Atlantis < 0.30.0; github.com/runatlantis/atlantis (Go) < 0.30.0, SEMVER:introduced=0,fixed=0.30.0.
Is there a fix for CVE-2024-52009?: Yes. github.com/runatlantis/atlantis (Go): upgrade to 0.30.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2024-52009 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2024-52009?: Check whether you run Atlantis or github.com/runatlantis/atlantis (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/runatlantis/atlantis (Go): upgrade to 0.30.0 or later
```
go get github.com/runatlantis/atlantis@v0.30.0
```

Technical details

A sensitive information leak (CWE-532) exists in Atlantis versions prior to 0.30.0. The vulnerability occurs in the GitHub App credential rotation logic within 'vcs/gh_app_creds_rotator.go', where the application logs the full 'ghs_' token at the debug level. An attacker with low-privileged network access to log aggregation tools (such as Argo CD or Kubernetes log viewers) can extract these tokens. These tokens grant the same permissions as the Atlantis GitHub App, potentially allowing full administrative access to managed GitHub organizations. The issue is fixed in version 0.30.0 by removing the sensitive logging.

Affected products

runatlantis atlantis < 0.30.0

Identifiers

CVE-2024-52009
GHSA-gppm-hq3p-h4rp
GO-2024-3265

Timeline

2024-11-08: advisory: GitHub Advisory GHSA-gppm-hq3p-h4rp published
2024-11-08: patched: Fix included in Atlantis v0.30.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.