# CVE-2024-23618: Arris SURFboard SBG6950AC2 Arbitrary Code Execution Vulnerability

> Unauthenticated attackers can achieve root code execution on Arris SURFboard SBG6950AC2 devices due to missing authentication.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jan 2024
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-r47x-9r32-fvp4

## What is CVE-2024-23618?

CVE-2024-23618 is a critical authentication bypass vulnerability in Arris SURFboard SBG6950AC2, published on 25 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An arbitrary code execution vulnerability exists in Arris SURFboard SGB6950AC2 devices. An unauthenticated attacker can exploit this vulnerability to achieve code execution as root.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Commscope Arris Surfboard Sbg6950ac2 Firmware.

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

No fix has been published for CVE-2024-23618 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-23618 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-23618 is a critical authentication bypass vulnerability in Arris SURFboard SBG6950AC2, published on 25 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-23618 in the wild and no public exploit code.

Affected product: Arris SURFboard SBG6950AC2. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-23618/ (Markdown: https://insights.sbomify.com/CVE-2024-23618/index.md)
```

## Sources

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

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