dbcve.org
Og410xa FirmwareOperating system · Ntt East

CVE-2022-22986

HIGH · 8.8 CVSS v3.1 Published 2022-03-31
Fix available
A fix is available. Upgrade to after 2.28 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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
Netcommunity OG410X and OG810X series (Netcommunity OG410Xa, OG410Xi, OG810Xa, and OG810Xi firmware Ver.2.28 and earlier) allow an attacker on the adjacent network to execute an arbitrary OS command via a specially crafted config file.

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

Command injection vulnerability in Netcommunity OG410X/OG810X series firmware versions 2.28 and earlier allows an adjacent network attacker to execute arbitrary OS commands by uploading a specially crafted config file to the affected device.

MitigationUpdate firmware to a version later than 2.28 if available; otherwise, implement strict network segmentation to limit access to the affected devices to only trusted personnel on the adjacent network.

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
Og410xa FirmwareOperating system
Affected:<= 2.28
Og410xi FirmwareOperating system
Affected:<= 2.28
Og810xa FirmwareOperating system
Affected:<= 2.28
Og810xi FirmwareOperating system
Affected:<= 2.28

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 checks

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

  1. Identify device model
    Check the device label, web interface, or SNMP inventory for the exact model number (OG410XA, OG410XI, OG810XA, or OG810XI)
    Affected if Device is one of these four models in the OG410X/OG810X series
  2. Check firmware version
    Access the device web interface or CLI and locate the firmware version information, typically found in System Status, Device Info, or About pages
    Affected if Firmware version is 2.28 or lower
  3. Verify config upload feature exposure
    Check if the device configuration upload functionality is accessible from the network. Look for settings related to config file import, backup/restore, or firmware updates in the web interface
    Affected if Config file upload feature is exposed and accessible on the network
  4. Assess network accessibility
    Review network segmentation and access controls to determine if the device management interface is reachable from adjacent network segments
    Affected if Device is reachable from adjacent network segments without strict access controls

A user is affected if they have an OG410X or OG810X series device running firmware version 2.28 or lower with the config upload feature accessible from an adjacent network.

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 a release after 2.28
Interim mitigation

Update firmware to a version later than 2.28 if available; otherwise, implement strict network segmentation to limit access to the affected devices to only trusted personnel on the adjacent network.

Recommended fix Moderate confidence

Firmware version newer than 2.28 (contact NTT for the exact fixed release)

  1. Identify the specific Netcommunity OG410X or OG810X device model (OG410Xa, OG410Xi, OG810Xa, or OG810Xi) in your environment
  2. Download the latest firmware version from the official NTT website (business.ntt-east.co.jp or www.ntt-west.co.jp)
  3. Review the firmware upgrade instructions in the product manual
  4. Upload the new firmware file through the device's web management interface or CLI
  5. Verify the firmware version after upgrade matches the fixed release
  6. Confirm the device is functioning normally after the update
Caveat Review release notes for any configuration changes required after upgrade; test in non-production environment first

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

Fix this in Og410xa Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22986 — 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-22986 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