CVE-2022-30272

The Motorola ACE1000 RTU through 2022-05-02 mishandles firmware integrity. It utilizes either the STS software suite or ACE1000 Easy Configurator for performing firmware updates. In case of the Easy Configurator, firmware updates are performed through access to the Web UI where file system, kernel, package, bundle, or application images can be installed. Firmware updates for the Front End Processor (FEP) module are performed via access to the SSH interface (22/TCP), where a .hex file image is transferred and a bootloader script invoked. File system, kernel, package, and bundle updates are supplied as RPM (RPM Package Manager) files while FEP updates are supplied as S-rec files. In all cases, firmware images were found to have no authentication (in the form of firmware signing) and only relied on insecure checksums for regular integrity checks.

CVSS v3 7.2 HIGH

7.2^/10

CVSS v3 : HIGH

Vector :

Exploitability : 1.2 / Impact : 5.9

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required HIGH

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact HIGH

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://www.cisa.gov/uscert/ics/advisories/icsa-22-179-06	Mitigation Third Party Advisory US Government Resource
https://www.forescout.com/blog/	Not Applicable

Configurations

Configuration 1 (hide)

AND

cpe:2.3:o:motorola:ace1000_firmware:-:*:*:*:*:*:*:*

cpe:2.3:h:motorola:ace1000:-:*:*:*:*:*:*:*

History

No history.

Information

Published : 2022-07-26 23:15

Updated : 2024-02-28 19:29

NVD link : CVE-2022-30272

Mitre link : CVE-2022-30272

CVE.ORG link : CVE-2022-30272

JSON object : View

Products Affected

motorola

ace1000
ace1000_firmware

CWE

CWE-345

Insufficient Verification of Data Authenticity

{"id": "CVE-2022-30272", "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.2, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "HIGH", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.2}]}, "published": "2022-07-26T23:15:08.217", "references": [{"url": "https://www.cisa.gov/uscert/ics/advisories/icsa-22-179-06", "tags": ["Mitigation", "Third Party Advisory", "US Government Resource"], "source": "cve@mitre.org"}, {"url": "https://www.forescout.com/blog/", "tags": ["Not Applicable"], "source": "cve@mitre.org"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "CWE-345"}]}], "descriptions": [{"lang": "en", "value": "The Motorola ACE1000 RTU through 2022-05-02 mishandles firmware integrity. It utilizes either the STS software suite or ACE1000 Easy Configurator for performing firmware updates. In case of the Easy Configurator, firmware updates are performed through access to the Web UI where file system, kernel, package, bundle, or application images can be installed. Firmware updates for the Front End Processor (FEP) module are performed via access to the SSH interface (22/TCP), where a .hex file image is transferred and a bootloader script invoked. File system, kernel, package, and bundle updates are supplied as RPM (RPM Package Manager) files while FEP updates are supplied as S-rec files. In all cases, firmware images were found to have no authentication (in the form of firmware signing) and only relied on insecure checksums for regular integrity checks."}, {"lang": "es", "value": "Motorola ACE1000 RTU hasta el 2022-05-02, maneja inapropiadamente la integridad del firmware. usa el paquete de software STS o el ACE1000 Easy Configurator para llevar a cabo las actualizaciones de firmware. En el caso del Easy Configurator, las actualizaciones de firmware son llevadas a cabo mediante el acceso a la Interfaz de Usuario Web, donde pueden instalarse im\u00e1genes del sistema de archivos, del kernel, del paquete, del bundle o de la aplicaci\u00f3n. Las actualizaciones de firmware para el m\u00f3dulo del procesador frontal (FEP) son llevadas a cabo por medio del acceso a la interfaz SSH (22/TCP), donde es transferida una imagen de archivo .hex y es invocado un script del cargador de arranque. Las actualizaciones del sistema de archivos, el kernel, los paquetes y los bundles se suministran como archivos RPM (RPM Package Manager), mientras que las actualizaciones del FEP son suministradas como archivos S-rec. En todos los casos, se ha detectado que las im\u00e1genes de firmware no ten\u00edan autenticaci\u00f3n (en forma de firma de firmware) y s\u00f3lo son basadas en sumas de comprobaci\u00f3n no seguras para las comprobaciones regulares de integridad"}], "lastModified": "2024-02-15T03:19:02.693", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:motorola:ace1000_firmware:-:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "D94120E5-38DE-44EF-B1D6-C418DC816D25"}], "operator": "OR"}, {"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:h:motorola:ace1000:-:*:*:*:*:*:*:*", "vulnerable": false, "matchCriteriaId": "D16356CC-9056-4675-8DBE-EF395A5529E8"}], "operator": "OR"}], "operator": "AND"}], "sourceIdentifier": "cve@mitre.org"}