# CVE-2024-5042: Submariner-operator: rbac permissions can allow for the spread of node compromises > Excessive RBAC permissions allow attackers to steal service account tokens and compromise other nodes or the entire cluster. - **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 17 May 2024 - **Updated:** 13 Oct 2026 - **Also known as:** GHSA-2rhx-qhxp-5jpw, GO-2024-2866 ## What is CVE-2024-5042? CVE-2024-5042 is a medium-severity vulnerability in Red Hat RHODF-4.16-RHEL-9, published on 17 May 2024. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description A flaw was found in the Submariner project. Due to unnecessary role-based access control permissions, a privileged attacker can run a malicious container on a node that may allow them to steal service account tokens and further compromise other nodes and potentially the entire cluster. Weakness: CWE-250 (Execution with Unnecessary Privileges) ## Which versions are affected by CVE-2024-5042? 9 open source packages ship an affected version, including github.com/submariner-io/submariner-operator. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/submariner-io/submariner-operator` | Go | All versions | 0.16.4 | | `github.com/submariner-io/submariner-operator` | Go | All versions | 0.15.4 | | `github.com/submariner-io/submariner-operator` | Go | All versions | 0.15.4 | | `github.com/submariner-io/submariner-operator` | Go | From 0.16.0-m0 | 0.16.4 | | `github.com/submariner-io/submariner-operator` | Go | From 0.16.0-m0 | 0.16.4 | | `github.com/submariner-io/submariner-operator` | Go | From 0.17.0-m0 | 0.17.2 | | `github.com/submariner-io/submariner-operator` | Go | From 0.17.0-m0 | 0.17.2 | | `github.com/submariner-io/submariner-operator` | Go | From 0.18.0-m0 | 0.18.0-rc0 | | `github.com/submariner-io/submariner-operator` | Go | From 0.18.0-m0 | 0.18.0-rc0 | ## How do I fix CVE-2024-5042? Upgrade github.com/submariner-io/submariner-operator to a fixed version for your release line: 0.16.4, 0.15.4, 0.17.2 or 0.18.0-rc0. ## Is CVE-2024-5042 being exploited? There is no known exploitation of CVE-2024-5042 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-5042 and fix it if it is affected. What it is: CVE-2024-5042 is a medium-severity vulnerability in Red Hat RHODF-4.16-RHEL-9, published on 17 May 2024. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-5042 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/submariner-io/submariner-operator (Go): affected all versions; fixed in 0.16.4 - github.com/submariner-io/submariner-operator (Go): affected all versions; fixed in 0.15.4 - github.com/submariner-io/submariner-operator (Go): affected all versions; fixed in 0.15.4 - github.com/submariner-io/submariner-operator (Go): affected from 0.16.0-m0; fixed in 0.16.4 - github.com/submariner-io/submariner-operator (Go): affected from 0.16.0-m0; fixed in 0.16.4 - github.com/submariner-io/submariner-operator (Go): affected from 0.17.0-m0; fixed in 0.17.2 - github.com/submariner-io/submariner-operator (Go): affected from 0.17.0-m0; fixed in 0.17.2 - github.com/submariner-io/submariner-operator (Go): affected from 0.18.0-m0; fixed in 0.18.0-rc0 - github.com/submariner-io/submariner-operator (Go): affected from 0.18.0-m0; fixed in 0.18.0-rc0 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-5042/ (Markdown: https://insights.sbomify.com/CVE-2024-5042/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5042 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5042 - OSV: https://osv.dev/vulnerability/CVE-2024-5042 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-5042/ Summaries are generated and may contain mistakes; the official description above is the record.