dbcve.org
Centrecom Ar260s FirmwareOperating system · Allied Telesis

CVE-2022-34869

HIGH · 8.8 CVSS v3.1 Published 2022-09-08
Fix available
A fix is available. Upgrade to 3.3.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Undocumented hidden command that can be executed from the telnet function of CentreCOM AR260S V2 firmware versions prior to Ver.3.3.7 allows a remote authenticated attacker to execute an arbitrary OS command.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An undocumented hidden command exists in the telnet function of CentreCOM AR260S V2 firmware versions prior to Ver.3.3.7, allowing a remote authenticated attacker to execute arbitrary OS commands with elevated privileges.

MitigationUpgrade CentreCOM AR260S V2 firmware to Ver.3.3.7 or later to remove the undocumented hidden command. If upgrade is not immediately possible, restrict telnet access to trusted IP addresses and disable telnet if SSH is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Centrecom Ar260s FirmwareOperating system
Affected:< 3.3.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Log into the device administrative interface or check the device label to confirm the model is CentreCOM AR260S V2.
    Affected if Device is not an AR260S V2, then not affected by this specific CVE.
  2. Check firmware version
    Access the device CLI or web interface and locate the firmware version information, typically shown in system status or device information pages.
    Affected if Firmware version is lower than 3.3.7 (e.g., 3.3.6, 3.3.5, etc.).
  3. Verify telnet service status
    Check the device configuration for telnet service settings, usually found under services, remote access, or network services configuration.
    Affected if Telnet is enabled and accessible on the device.

A device is affected if it is a CentreCOM AR260S V2 running firmware version lower than 3.3.7 with telnet service enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.3.7 or later
Fixed in 3.3.7
Interim mitigation

Upgrade CentreCOM AR260S V2 firmware to Ver.3.3.7 or later to remove the undocumented hidden command. If upgrade is not immediately possible, restrict telnet access to trusted IP addresses and disable telnet if SSH is available.

Recommended fix High confidence

Firmware version 3.3.7 (or later) for CentreCOM AR260S V2

  1. 1. Identify the current firmware version of the CentreCOM AR260S device by accessing the web management interface or using the 'show version' command via console/telnet.
  2. 2. Navigate to the official Allied Telesis support website (www.allied-telesis.co.jp) and locate the firmware download section for the AR260S product.
  3. 3. Download firmware version 3.3.7 or later for the CentreCOM AR260S V2.
  4. 4. Consult the product's firmware upgrade manual for the official upgrade procedure, which typically involves accessing the web management interface and using the firmware update function, or using TFTP/console methods.
  5. 5. Apply the firmware upgrade following the vendor's documented steps, ensuring stable power during the process.
  6. 6. After the device reboots, verify the new firmware version is 3.3.7 or later using 'show version'.
  7. 7. Confirm the hidden undocumented command vulnerability is no longer present by testing that the specific hidden command is rejected or no longer functional.
Caveat Standard firmware upgrade risks apply - ensure configuration backup before upgrade and plan for brief downtime; verify all functionality works post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Centrecom Ar260s Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,590
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34869 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34869 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data