CVE-2022-38394
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 · uneditedUse 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.
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 confidenceThe CentreCOM AR260S V2 router firmware versions prior to 3.3.7 contain hard-coded credentials for the embedded telnet server, allowing remote unauthenticated attackers to gain full OS command execution capabilities.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify the installed firmware versionAccess the router's web management interface or CLI and locate the firmware version information, typically found under System > Status or using the 'show version' commandAffected if The firmware version is lower than 3.3.7 (for example, 3.3.5, 3.3.0, or earlier)
-
Confirm telnet server is enabledCheck the router's configuration for telnet service settings, usually under Services or Management access settings in the web interface or via 'show running-config' in CLIAffected if Telnet service is enabled and accessible from network interfaces
-
Verify telnet access credentialsAttempt to connect to the device's telnet port (port 23) using the known hardcoded credentials or check if default credentials are still in useAffected if Default or hardcoded credentials (such as admin/manager or similar vendor defaults) are still active for telnet access
-
Review management access restrictionsCheck firewall or access control lists that govern which IP addresses can reach the telnet serviceAffected if Telnet is exposed to untrusted networks or the internet without IP restrictions
The device is affected if the firmware version is below 3.3.7 AND telnet server is enabled with default or hardcoded credentials accessible from the network
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
Update firmware to version 3.3.7 or later, change default credentials, and consider disabling telnet in favor of secure management protocols like SSH.
CentreCOM AR260S V2 firmware Ver.3.3.7 or later
- Obtain the firmware version 3.3.7 or later for CentreCOM AR260S from the official Allied Telesis website (www.allied-telesis.co.jp) or authorized distribution channel
- Access the device's web-based management interface or console
- Navigate to the firmware upgrade or system maintenance section
- Upload the firmware file version 3.3.7 or later
- Apply the firmware update and allow the device to reboot
- After reboot, verify the firmware version has been updated to 3.3.7 or later
- Change any default credentials post-upgrade as per vendor best practices
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38394 — 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-38394 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