CVE-2022-35273
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 GUI setting page 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 GUI setting page of CentreCOM AR260S V2 router firmware allows remote authenticated attackers to inject and execute arbitrary operating system commands through unsanitized input fields in the web management interface.
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.
-
Identify the device modelAccess the router's web management interface and locate the system status or device information page to confirm the model is CentreCOM AR260SAffected if The device is an CentreCOM AR260S V2 router
-
Check the installed firmware versionIn the web management interface, navigate to the firmware or system information page and note the displayed firmware version numberAffected if The firmware version is lower than 3.3.7 (for example, 3.3.6, 3.3.5, etc.)
-
Confirm the web management interface is accessibleAttempt to access the router's web GUI by entering the device IP address in a web browserAffected if The web management interface is reachable from the network being tested
-
Verify remote administrative access is enabledIn the web management interface, check the administrative access or remote management settings to determine if remote web access is permittedAffected if Remote administrative access to the web interface is enabled for external or untrusted IP addresses
The environment is affected if the device is a CentreCOM AR260S with firmware version lower than 3.3.7 and the web management interface is accessible with administrative credentials.
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 firmware to Ver.3.3.7 or later. If immediate upgrade is not feasible, restrict administrative access to the web interface to trusted/internal IP addresses only to reduce attack surface.
Firmware Ver.3.3.7
- Obtain the official firmware version 3.3.7 or later for CentreCOM AR260S from the Allied Telesis support website (www.allied-telesis.co.jp)
- Access the CentreCOM AR260S device web-based administration interface
- Navigate to the System Maintenance or Firmware Upgrade section
- Upload and apply firmware version 3.3.7 or later
- Allow the device to complete the upgrade process and reboot
- Verify the device is running the updated firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35273 — 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-35273 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