# CVE-2017-2125: Privilege escalation in CentreCOM

> Authenticated attackers can escalate privileges via the guest account on Allied Telesis CentreCOM AR260S V2 routers.

- **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:** 28 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r22m-g7h4-h52r

## What is CVE-2017-2125?

CVE-2017-2125 is a high-severity vulnerability in Allied Telesis K.K. CentreCOM, published on 28 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Privilege escalation vulnerability in CentreCOM AR260S V2 remote authenticated attackers to gain privileges via the guest account.

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

It affects 1 product.


Products: Allied Telesis K.k. Centrecom Ar260s V2 Firmware.

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

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

## Is CVE-2017-2125 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-2125 is a high-severity vulnerability in Allied Telesis K.K. CentreCOM, published on 28 Apr 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-2125 in the wild and no public exploit code.

Affected product: Allied Telesis K.K. CentreCOM. 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-2125/ (Markdown: https://insights.sbomify.com/CVE-2017-2125/index.md)
```

## Sources

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

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