AI analysis
Armatura One can store database and message-broker credentials in an install configuration file and, when that protection is enabled, encrypt them with AES-128-CBC. The encryption key and initialization vector are fixed values embedded in the software and are the same on every installation, so anyone with a copy of the installation package can recover them. An attacker who also obtains a specific site’s encrypted configuration file can decrypt that site’s stored credentials and then use them against the database and message broker. The issue is assigned to Armatura LLC’s Armatura One; no affected version range is stated in the advisory data. It is not listed in CISA KEV, and no public proof-of-concept is known.
What to do: Treat the built-in AES protection as ineffective: restrict local access to the Armatura One install configuration file, and rotate the database and message-broker credentials if that file may have been copied. Apply any vendor fix when Armatura publishes one, and do not rely on the current encryption to keep those secrets confidential from anyone who also has the installation package.
Affected
| Armatura LLC Armatura One | — |
Estimated exposure
—No basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description
Armatura One stores database and message-broker credentials in an install configuration file, encrypting them with AES-128-CBC when this protection is enabled. The encryption key and initialization vector are fixed values embedded in the software itself and are identical across every installation. An attacker with a copy of the installation package can recover this key and initialization vector, and can then decrypt the stored credentials of any specific installation to which the attacker separately obtains the encrypted configuration file.