LiveActive security incident?Get immediate response
CVE Record

CVE-2020-21883: Unibox U-50 2.4 and UniBox Enterprise Series 2.4 and UniBox Campus Series 2.4 contain a OS command injectio...

Unibox U-50 2.4 and UniBox Enterprise Series 2.4 and UniBox Campus Series 2.4 contain a OS command injection vulnerability in /tools/ping, which can leads to complete device takeover.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-21883 is an OS command injection issue in the /tools/ping function of Unibox U-50 2.4, UniBox Enterprise Series 2.4, and UniBox Campus Series 2.4. The CVE description says successful abuse can lead to complete device takeover. Public metadata does not provide CVSS scoring or confirm active exploitation.

Executive priority

Treat this as a high-priority appliance risk if affected devices exist, especially if reachable beyond a trusted admin network. The business concern is potential device takeover. Priority can be lowered only after confirming no affected version, no reachable interface, or an applied vendor fix or effective isolation.

Technical view

The vulnerability is described as command injection in a web-exposed ping tool path, /tools/ping. Affected versions named in the CVE title and description are 2.4 of Unibox U-50, UniBox Enterprise Series, and UniBox Campus Series. The CVE record lacks structured CPEs, CWE mapping, CVSS, authentication context, and vendor patch details.

Likely exposure

Exposure is most likely where affected UniBox appliances running version 2.4 have their web management or tools interface reachable by users or networks that should not administer the device. Internet-facing or broadly reachable interfaces would raise urgency. The source bundle does not confirm affected deployments beyond the named products and version.

Exploitation context

The public CVE description and linked advisory state command injection with possible complete takeover. However, CISA KEV is false in the provided data, and no cited source confirms active exploitation. Public references appear to include disclosure material, so defenders should assume technical details may be available publicly.

Researcher notes

Evidence is limited but direct: the CVE and linked disclosures identify product/version and vulnerable path. Missing items include CVSS, CWE, CPEs, authentication requirements, and patch status. Avoid assuming exploitation in the wild; KEV is false in the provided data. Validation should focus on asset identification, reachability, and vendor confirmation.

Mitigation direction

  • Check vendor or support guidance for fixed firmware or official workarounds.
  • Restrict access to UniBox web management interfaces to trusted administrative networks.
  • Place affected devices behind VPN, firewall ACLs, or equivalent access controls.
  • Monitor for suspicious use of the ping tool or unexpected device behavior.
  • If no supported fix exists, plan isolation, decommissioning, or replacement.

Validation and detection

  • Inventory for Unibox U-50, Enterprise Series, and Campus Series devices running 2.4.
  • Confirm whether /tools/ping is reachable from untrusted networks.
  • Review web access logs for unusual requests to the ping tool.
  • Verify whether vendor guidance identifies a fixed firmware or workaround.
  • Document compensating controls for any device that cannot be patched.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-21883 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.