Recoverable credential storage in Mobotix Control Center exposes administrative access

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

Overview

Original source data

Mobotix Control Center (MxCC) through 2.5.4.5 has Insufficiently Protected Credentials, Storing Passwords in a Recoverable Format via the MxCC.ini config file. The credential storage method in this software enables an attacker/user of the machine to gain admin access to the software and gain access to recordings/recording locations.

Affected products and scope

  • Mobotix Control Center (MxCC): affected through and including version 2.5.4.5.
  • NVD describes the affected boundary with a version end at 2.5.4.5; the available evidence does not confirm the status of parallel release branches or later versions.
  • No other affected Mobotix product is identified in the record.

Technical details

This is insufficient protection of stored credentials, classified as CWE-522. When MxCC saves its configuration, passwords are written to the MxCC.ini file in reversible Base64 form rather than protected with a non-recoverable mechanism. The exposed values include MxCC user passwords, camera passwords, and network share passwords. The configuration file is present on the workstation and may also be copied to backup locations, so a user, process, or attacker able to access the workstation, file, or backup may recover the credentials. The available evidence does not establish whether operating-system permissions, file ownership, or additional protection mechanisms limit access to MxCC.ini in a particular deployment.

Exploitability

The normalized record marks a public exploit as available, and the public technical material describes recovery of password values from the configuration file. The supplied attack characteristics describe network reachability, low complexity, low required privileges, and no user interaction. However, the technical analysis centers on reading a local configuration file or backup, so practical reachability depends on access to the workstation, file, or relevant application context. The available evidence does not confirm exploitation in the wild, a specific campaign, or a named victim.

Technical impact

An attacker or user may read the configuration file and recover credentials in cleartext. Recovered MxCC user credentials may provide administrative access within the application, while camera and network share credentials may enable unauthorized access to devices, recordings, or storage locations. The resulting privilege and scope depend on the role of the stored account and the permissions of the associated resources. The available evidence does not establish operating-system compromise, lateral movement, or a specific breach.

Business impact

Exposed credentials may enable unauthorized access to MxCC user accounts, camera devices, and network shares configured for remote storage. An MxCC account with administrative rights may increase the impact within the application, while camera or network share credentials may expose recordings and their storage locations. Organizations may need to protect recorded data, rotate multiple groups of credentials, and review configuration backups. The actual scope depends on the privileges of the recovered accounts and the resources they can access. The available evidence does not confirm a specific intrusion or data breach.

Remediation

  1. Upgrade to an official fixed release if Mobotix provides one: the available record does not identify a fixed release or specific patch, so a newer version should not be assumed to resolve the issue without confirmation.
  2. Until confirmed vendor guidance or a fix is available, restrict read access to MxCC.ini, its containing directory, and all configuration backups. Do not keep those copies where unauthorized users or processes can access them.
  3. Rotate passwords for MxCC accounts, cameras, and network shares that were stored in affected configuration files or backups. Prioritize passwords reused in other systems.
  4. Review and securely dispose of older backups containing stored credentials, and verify that newly generated configuration files no longer contain recoverable secrets.
  5. After remediation, recheck file permissions, MxCC accounts, camera connections, and recording locations. Do not treat the absence of suspicious logs as proof that old credentials were not collected.

Detection

  1. Inventory workstations running Mobotix Control Center and compare installed versions with the affected range.
  2. Locate MxCC.ini in the user's application-data directory and in configuration backup locations. Inspect for sections such as [UsersnGroups], Password fields, and @ByteArray values.
  3. Determine whether the files contain MxCC user, camera, or network share credentials. If they do, treat those credentials as exposed and rotate them.
  4. Review read permissions, ownership, and access history for the configuration file and its backups. The absence of suspicious access records does not prove that the credentials were not read.
  5. Additional monitoring of access to the configuration file and backups may be used as a precaution, but the available record does not provide a specific IOC or log event.
Sources (21)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.