ID CVE-2018-5399
Summary The Auto-Maskin DCU 210E firmware contains an undocumented Dropbear SSH server, v2015.55, configured to listen on Port 22 while the DCU is running. The Dropbear server is configured with a hard-coded user name and password combination of root / amroot. The server is configured to use password only authentication not cryptographic keys, however the firmware image contains an RSA host-key for the server. An attacker can exploit this vulnerability to gain root access to the Angstrom Linux operating system and modify any binaries or configuration files in the firmware. Affected releases are Auto-Maskin DCU-210E RP-210E: Versions prior to 3.7 on ARMv7.
References
Vulnerable Configurations
  • cpe:2.3:o:auto-maskin:dcu-210e_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:auto-maskin:dcu-210e_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:auto-maskin:dcu-210e:-:*:*:*:*:*:*:*
    cpe:2.3:h:auto-maskin:dcu-210e:-:*:*:*:*:*:*:*
  • cpe:2.3:o:auto-maskin:rp-210e_firmware:*:*:*:*:*:*:*:*
    cpe:2.3:o:auto-maskin:rp-210e_firmware:*:*:*:*:*:*:*:*
  • cpe:2.3:h:auto-maskin:rp-210e:-:*:*:*:*:*:*:*
    cpe:2.3:h:auto-maskin:rp-210e:-:*:*:*:*:*:*:*
CVSS
Base: 10.0 (as of 09-10-2019 - 23:41)
Impact:
Exploitability:
CWE CWE-798
CAPEC
  • Try Common or Default Usernames and Passwords
    An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. "secret" or "password") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.
  • Read Sensitive Strings Within an Executable
    An adversary engages in activities to discover any sensitive strings are present within the compiled code of an executable, such as literal ASCII strings within the file itself, or possibly strings hard-coded into particular routines that can be revealed by code refactoring methods including static and dynamic analysis. One specific example of a sensitive string is a hard-coded password. Typical examples of software with hard-coded passwords include server-side executables which may check for a hard-coded password or key during a user's authentication with the server. Hard-coded passwords can also be present in client-side executables which utilize the password or key when connecting to either a remote component, such as a database server, licensing server, or otherwise, or a processes on the same host that expects a key or password. When analyzing an executable the adversary may search for the presence of such strings by analyzing the byte-code of the file itself. Example utilities for revealing strings within a file include 'strings,' 'grep,' or other variants of these programs depending upon the type of operating system used. These programs can be used to dump any ASCII or UNICODE strings contained within a program. Strings can also be searched for using a hex editors by loading the binary or object code file and utilizing native search functions such as regular expressions.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
COMPLETE COMPLETE COMPLETE
cvss-vector via4 AV:N/AC:L/Au:N/C:C/I:C/A:C
refmap via4
cert-vn VU#176301
misc https://www.us-cert.gov/ics/advisories/icsa-20-051-04
Last major update 09-10-2019 - 23:41
Published 08-10-2018 - 15:29
Last modified 09-10-2019 - 23:41
Back to Top