# CVE-2017-11169: Privilege escalation in n/a

> Authenticated users can gain root privileges on iBall routers by manipulating a parameter in the user configuration interface.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-pw7x-gq4w-96vp

## What is CVE-2017-11169?

CVE-2017-11169 is a high-severity vulnerability in n/a, published on 13 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Privilege Escalation on iBall iB-WRA300N3GT iB-WRA300N3GT_1.1.1 devices allows remote authenticated users to obtain root privileges by leveraging a guest/user/normal account to submit a modified privilege parameter to /form2userconfig.cgi.

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

It affects 1 product.


Products: Iball Ib-Wra300n3gt Firmware.

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

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

## Is CVE-2017-11169 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-11169 is a high-severity vulnerability in n/a, published on 13 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-11169 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-11169/ (Markdown: https://insights.sbomify.com/CVE-2017-11169/index.md)
```

## Sources

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

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