CVE-2024-47060: Github.com/zitadel/zitadel/v2 ZITADEL Allows Unauthorized Access After Vulnerability

HIGH
Advisory Identifier: GHSA-jj94-6f5c-65r8
CVSS 6.8
CWE-672 CWE-200
Published
Advisory Summary

CVE-2024-47060 is a HIGH (CVSS 6.8) zitadel allows unauthorized access after vulnerability (CWE-672: Operation on a Resource after Expiration or Release) affecting Github.com/zitadel/zitadel/v2 libraries in the Go ecosystem. The issue involves zitadel allows unauthorized access after organization or project deactivation. Remediation is available by upgrading affected packages to version 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, 2.54.10.

CVE-2024-47060 at a Glance

CVE Identifier CVE-2024-47060
GHSA Identifier GHSA-jj94-6f5c-65r8
Severity HIGH
CVSS v3.1 Base Score 6.8
CWE Classification CWE-672: Operation on a Resource after Expiration or Release
Affected Product Github.com/zitadel/zitadel/v2
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2024-47060

To remediate this vulnerability, upgrade all affected Github.com/zitadel/zitadel/v2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/zitadel/zitadel/v2 fixed: 2.62.1
Upgrade github.com/zitadel/zitadel/v2 to 2.62.1
github.com/zitadel/zitadel/v2 fixed: 2.61.1
Upgrade github.com/zitadel/zitadel/v2 to 2.61.1
github.com/zitadel/zitadel/v2 fixed: 2.60.2
Upgrade github.com/zitadel/zitadel/v2 to 2.60.2
github.com/zitadel/zitadel/v2 fixed: 2.59.3
Upgrade github.com/zitadel/zitadel/v2 to 2.59.3
github.com/zitadel/zitadel/v2 fixed: 2.58.5
Upgrade github.com/zitadel/zitadel/v2 to 2.58.5
github.com/zitadel/zitadel/v2 fixed: 2.57.5
Upgrade github.com/zitadel/zitadel/v2 to 2.57.5
github.com/zitadel/zitadel/v2 fixed: 2.56.6
Upgrade github.com/zitadel/zitadel/v2 to 2.56.6
github.com/zitadel/zitadel/v2 fixed: 2.55.8
Upgrade github.com/zitadel/zitadel/v2 to 2.55.8
github.com/zitadel/zitadel/v2 fixed: 2.54.10
Upgrade github.com/zitadel/zitadel/v2 to 2.54.10
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/zitadel/zitadel/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2024-47060, inspect your project dependencies for Github.com/zitadel/zitadel/v2:

inspect dependencies for github.com/zitadel/zitadel/v2

Analyze the terminal output to locate any version of Github.com/zitadel/zitadel/v2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.62.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-672: Operation on a Resource after Expiration or Release, where the product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. In Github.com/zitadel/zitadel/v2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary In Zitadel, even after an organization is deactivated, associated projects, respectively their applications remain active. Users across other organizations can still log in and access through these applications, leading to unauthorized access. Additionally, if a project was deactivated access to applications was also still possible. ### Details The issue stems from the fact that when an organization is deactivated in Zitadel, the applications associated with it do not automatically deactivate. The application lifecycle is not tightly coupled with the organization's lifecycle, leading to a situation where the organization or project is marked as inactive, but its resources remain accessible. ### PoC - Create a new Organization, create new project and setup OpenID connect. - Deactivate an Organization - Setup authentication without selecting Check for Project on Authentication - User is able to login despite the organization is deactivated ### Impact This vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation. ### Patches 2.x versions are fixed on >= [2.62.1](https://github.com/zitadel/zitadel/releases/tag/v2.62.1) 2.61.x versions are fixed on >= [2.61.1](https://github.com/zitadel/zitadel/releases/tag/v2.61.1) 2.60.x versions are fixed on >= [2.60.2](https://github.com/zitadel/zitadel/releases/tag/v2.60.2) 2.59.x versions are fixed on >= [2.59.3](https://github.com/zitadel/zitadel/releases/tag/v2.59.3) 2.58.x versions are fixed on >= [2.58.5](https://github.com/zitadel/zitadel/releases/tag/v2.58.5) 2.57.x versions are fixed on >= [2.57.5](https://github.com/zitadel/zitadel/releases/tag/v2.57.5) 2.56.x versions are fixed on >= [2.56.6](https://github.com/zitadel/zitadel/releases/tag/v2.56.6) 2.55.x versions are fixed on >= [2.55.8](https://github.com/zitadel/zitadel/releases/tag/v2.55.8) 2.54.x versions are fixed on >= [2.54.10](https://github.com/zitadel/zitadel/releases/tag/v2.54.10) ### Workaround Unpatched versions can explicitly disable the application to make sure the client is not allowed anymore. ### Questions If you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com) ### Credits Thanks to @prdp1137 for reporting this!

CVE-2024-47060 Affected Github.com/zitadel/zitadel/v2 Versions

9 component(s)
Fixed Versions:
2.62.12.61.12.60.22.59.32.58.52.57.52.56.62.55.82.54.10
Product / Package Ecosystem Affected Versions Fixed Version
github.com/zitadel/zitadel/v2
Go
≥ 2.62.0
< 2.62.1
2.62.1
github.com/zitadel/zitadel/v2
Go
≥ 2.61.0
< 2.61.1
2.61.1
github.com/zitadel/zitadel/v2
Go
≥ 2.60.0
< 2.60.2
2.60.2
github.com/zitadel/zitadel/v2
Go
≥ 2.59.0
< 2.59.3
2.59.3
github.com/zitadel/zitadel/v2
Go
≥ 2.58.0
< 2.58.5
2.58.5
github.com/zitadel/zitadel/v2
Go
≥ 2.57.0
< 2.57.5
2.57.5
github.com/zitadel/zitadel/v2
Go
≥ 2.56.0
< 2.56.6
2.56.6
github.com/zitadel/zitadel/v2
Go
≥ 2.55.0
< 2.55.8
2.55.8
github.com/zitadel/zitadel/v2
Go
< 2.54.10
2.54.10

References

Frequently Asked Questions

What is CVE-2024-47060?
CVE-2024-47060 is a security vulnerability in Github.com/zitadel/zitadel/v2 involving ZITADEL Allows Unauthorized Access After Organization or Project Deactivation under CWE-672: Operation on a Resource after Expiration or Release.
Which Github.com/zitadel/zitadel/v2 versions are affected?
Affected versions include releases prior to 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, 2.54.10 across affected packages: github.com/zitadel/zitadel/v2.
What version fixes CVE-2024-47060?
Upgrading to 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, 2.54.10 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/zitadel/zitadel/v2 affected?
Yes, github.com/zitadel/zitadel/v2 is affected in releases prior to 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, 2.54.10. Upgrade your dependency to 2.62.1, 2.61.1, 2.60.2, 2.59.3, 2.58.5, 2.57.5, 2.56.6, 2.55.8, 2.54.10 or later.
What is the CVSS score of CVE-2024-47060?
CVE-2024-47060 has a CVSS v3.1 base score of 6.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2024-47060?
CVE-2024-47060 is classified under CWE-672: Operation on a Resource after Expiration or Release (The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.).
How can I check Go dependencies for CVE-2024-47060?
Run the dependency tree command: 'inspect dependencies for github.com/zitadel/zitadel/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jj94-6f5c-65r8",
  "modified" : "2024-11-18T16:27:15Z",
  "published" : "2024-09-19T16:08:38Z",
  "aliases" : [ "CVE-2024-47060" ],
  "summary" : "ZITADEL Allows Unauthorized Access After Organization or Project Deactivation",
  "details" : "### Summary\nIn Zitadel, even after an organization is deactivated, associated projects, respectively their applications remain active. Users across other organizations can still log in and access through these applications, leading to unauthorized access.\nAdditionally, if a project was deactivated access to applications was also still possible.\n\n### Details\nThe issue stems from the fact that when an organization is deactivated in Zitadel, the applications associated with it do not automatically deactivate. The application lifecycle is not tightly coupled with the organization's lifecycle, leading to a situation where the organization or project is marked as inactive, but its resources remain accessible.\n\n### PoC\n- Create a new Organization, create new project and setup OpenID connect.\n- Deactivate an Organization\n- Setup authentication without selecting Check for Project on Authentication\n- User is able to login despite the organization is deactivated\n\n### Impact\nThis vulnerability allows for unauthorized access to projects and their resources, which should have been restricted post-organization deactivation.\n\n### Patches\n\n2.x versions are fixed on >= [2.62.1](https://github.com/zitadel/zitadel/releases/tag/v2.62.1)\n2.61.x versions are fixed on >= [2.61.1](https://github.com/zitadel/zitadel/releases/tag/v2.61.1)\n2.60.x versions are fixed on >= [2.60.2](https://github.com/zitadel/zitadel/releases/tag/v2.60.2)\n2.59.x versions are fixed on >= [2.59.3](https://github.com/zitadel/zitadel/releases/tag/v2.59.3)\n2.58.x versions are fixed on >= [2.58.5](https://github.com/zitadel/zitadel/releases/tag/v2.58.5)\n2.57.x versions are fixed on >= [2.57.5](https://github.com/zitadel/zitadel/releases/tag/v2.57.5)\n2.56.x versions are fixed on >= [2.56.6](https://github.com/zitadel/zitadel/releases/tag/v2.56.6)\n2.55.x versions are fixed on >= [2.55.8](https://github.com/zitadel/zitadel/releases/tag/v2.55.8)\n2.54.x versions are fixed on >= [2.54.10](https://github.com/zitadel/zitadel/releases/tag/v2.54.10)\n\n### Workaround\nUnpatched versions can explicitly disable the application to make sure the client is not allowed anymore.\n\n### Questions\nIf you have any questions or comments about this advisory, please email us at [security@zitadel.com](mailto:security@zitadel.com)\n\n### Credits\nThanks to @prdp1137 for reporting this!\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.62.0"
      }, {
        "fixed" : "2.62.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.61.0"
      }, {
        "fixed" : "2.61.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.60.0"
      }, {
        "fixed" : "2.60.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.59.0"
      }, {
        "fixed" : "2.59.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.58.0"
      }, {
        "fixed" : "2.58.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.57.0"
      }, {
        "fixed" : "2.57.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.56.0"
      }, {
        "fixed" : "2.56.6"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.55.0"
      }, {
        "fixed" : "2.55.8"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.54.10"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/security/advisories/GHSA-jj94-6f5c-65r8"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-47060"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/zitadel/zitadel"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200", "CWE-672" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-09-19T16:08:38Z",
    "nvd_published_at" : "2024-09-20T00:15:03Z"
  }
}