CVE-2022-38094
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 · uneditedOS command injection vulnerability in 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 confidenceOS command injection vulnerability in the telnet function of CentreCOM AR260S V2 router firmware allows remote authenticated attackers to execute arbitrary OS commands due to insufficient input sanitization in the telnet service.
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< 3.3.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device is CentreCOM AR260S V2Access the router admin interface or CLI and verify the model number in system information or device statusAffected if Device is not a CentreCOM AR260S V2 router
-
Check installed firmware versionLocate the firmware version displayed in the router's web interface under System Info or in the CLI outputAffected if Firmware version is below 3.3.7
-
Verify telnet service statusCheck the router's service configuration or security settings to determine if telnet is enabledAffected if Telnet service is currently enabled on the device
-
Assess telnet access exposureReview network access settings, firewall rules, or interface bindings to determine if telnet is accessible from external networksAffected if Telnet is exposed to untrusted or external network segments
Device is affected if it is a CentreCOM AR260S V2 running firmware version lower than 3.3.7 with telnet service enabled and network-accessible
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.3.7
Upgrade CentreCOM AR260S V2 firmware to Ver.3.3.7 or later. If immediate patching is not feasible, disable or restrict telnet access and implement network segmentation to limit exposure.
Ver.3.3.7
- Obtain firmware version 3.3.7 or later for CentreCOM AR260S from the official Allied Telesis support website (www.allied-telesis.co.jp)
- Access the device management interface and navigate to the firmware upgrade section
- Upload and apply the firmware version 3.3.7 following the vendor's documented upgrade procedure
- After reboot, verify the firmware version is 3.3.7 or later by checking the device status
- Confirm the telnet service is functioning properly and the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-38094 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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