# CVE-2017-9494: Security feature bypass in n/a

> Remote attackers can enable a hidden web inspector on Motorola cable modems, potentially allowing unauthorized access and control.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v8cp-8v4q-6gq4

## What is CVE-2017-9494?

CVE-2017-9494 is a medium-severity vulnerability in n/a, published on 31 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Comcast firmware on Motorola MX011ANM (firmware version MX011AN_2.9p6s1_PROD_sey) devices allows remote attackers to enable a Remote Web Inspector that is accessible from the public Internet.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2017-9494?

It affects 1 product.


Products: Motorola Mx011anm Firmware.

## How do I fix CVE-2017-9494?

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

## Is CVE-2017-9494 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9495](https://insights.sbomify.com/CVE-2017-9495/): Information disclosure in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9494 and fix it if it is affected.

What it is: CVE-2017-9494 is a medium-severity vulnerability in n/a, published on 31 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9494 in the wild and no public exploit code.

Affected product: n/a. 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-2017-9494/ (Markdown: https://insights.sbomify.com/CVE-2017-9494/index.md)
```

## Sources

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

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