Vulnerability Note VU#549807
Impero Education Pro classroom management software vulnerable to remote code execution
Original Release date: 09 Sep 2015 | Last revised: 10 Sep 2015
Impero Software Education Pro classroom management software is vulnerable to remote code execution via improper encryption and authentication mechanisms.
CWE-321: Use of Hard-coded Cryptographic Key
CWE-329: Not Using a Random IV with CBC Mode – CVE-2015-5997
According to the reporter, Impero uses a custom encryption protocol derived from AES-128 CBC. However, the AES implementation uses a hard-coded encryption key and initialization vector that are both derived from the SHA512 of the string "Imp3ro". Use of these hard-coded encryption values common to all instances of Impero allows an attacker to decrypt packets.
CWE-287: Improper Authentication – CVE-2015-5998
According to the reporter, authentication is performed only by sending the message "-1|AUTHENTICATE\x02PASSWORD". As this message may be spoofed once the encryption method is known, this authentication method is insufficient properly perform authentication.
Once authentication is gained, the attacker may execute Impero commands. These Impero commands include the ability to run programs with SYSTEM privileges, which an attacker may be able to use to remotely execute code.
According to Impero Software, Impero 5008 and below are vulnerable.
A remote unauthenticated attacker may be able to execute commands on the machine running Impero.
Apply an update
Impero has released Impero 5105 to address this issue. Affected users are encouraged to update to Impero 5105 or later as soon as possible. Affected users may contact Impero Software support for more information and to obtain the update.
Vendor Information (Learn More)
VendorStatusDate NotifiedDate UpdatedImperoAffected29 Jul 201501 Sep 2015If you are a vendor and your product is affected, let
CVSS Metrics (Learn More)
Thanks to slipstream/RoL for reporting this vulnerability.
This document was written by Garret Wassermann.
14 Jul 2015
Date First Published:
09 Sep 2015
Date Last Updated:
10 Sep 2015
FeedbackIf you have feedback, comments, or additional information about this vulnerability, please send us email.