CVE Intelligence
Skip to main content
MEDIUM

CVE-2020-24552

CVE-2020-24552 — Atop Technology 3G/4G LTE Cellular to Ethernet and Serial Secure Industrial Gateway - Command Injection

Atop Technology industrial 3G/4G gateway contains Command Injection vulnerability. Due to insufficient input validation, the device's web management interface allows attackers to inject specific code and execute system commands without privilege.

Published Updated Sources: cvelistV5, twcert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

atop technology

7 products listed

CVSS base

5.5

MEDIUM

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

Products (7)

3g 4g lte cellular to ethernet and serial secure industrial gateway se59013g 4g lte cellular to ethernet and serial secure industrial gateway se5901b3g 4g lte cellular to ethernet and serial secure industrial gateway se5904d3g 4g lte cellular to ethernet and serial secure industrial gateway se59083g 4g lte cellular to ethernet and serial secure industrial gateway se5908a3g 4g lte cellular to ethernet and serial secure industrial gateway se59163g 4g lte cellular to ethernet and serial secure industrial gateway se5916a

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
5.5CVSS 3.1MEDIUMcvelistV5

Weakness & attack patterns

  • CWE-78

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /4G.

References

1 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.