# CVE-2022-38394: Hardcoded credentials in CentreCOM AR260S V2

> Remote attackers can execute arbitrary OS commands on Allied Telesis CentreCOM AR260S V2 routers due to hard-coded telnet credentials.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-x5m2-f2v4-5h4p

## What is CVE-2022-38394?

CVE-2022-38394 is a critical vulnerability in Allied Telesis K.K. CentreCOM AR260S V2, published on 8 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of hard-coded credentials for the telnet server of CentreCOM AR260S V2 firmware versions prior to Ver.3.3.7 allows a remote unauthenticated attacker to execute an arbitrary OS command.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-38394?

It affects 1 product.


Products: Allied-Telesis Centrecom Ar260s Firmware.

## How do I fix CVE-2022-38394?

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

## Is CVE-2022-38394 being exploited?

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

## Other vulnerabilities in Allied Telesis K.K. CentreCOM AR260S V2

- [CVE-2022-34869](https://insights.sbomify.com/CVE-2022-34869/): Command injection in CentreCOM AR260S V2 (high 8.8)
- [CVE-2022-35273](https://insights.sbomify.com/CVE-2022-35273/): Command injection in CentreCOM AR260S V2 (high 8.8)
- [CVE-2022-38094](https://insights.sbomify.com/CVE-2022-38094/): Command injection in CentreCOM AR260S V2 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-38394 and fix it if it is affected.

What it is: CVE-2022-38394 is a critical vulnerability in Allied Telesis K.K. CentreCOM AR260S V2, published on 8 Sep 2022. 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-2022-38394 in the wild and no public exploit code.

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

## Sources

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

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