Use of Default Cryptographic Key

Opis

The product uses a default cryptographic key for potentially critical functionality.

It is common practice for products to be designed to use default keys. The rationale is to simplify the manufacturing process or the system administrator's task of installation and deployment into an enterprise. However, if admins do not change the defaults, it is easier for attackers to bypass authentication quickly across multiple organizations.

Skutki

• Authentication

  Gain Privileges or Assume Identity

Zapobieganie

• Requirements

  Prohibit use of default, hard-coded, or other values that do not vary for each installation of the product - especially for separate organizations.

  Skuteczność: High

• Architecture and Design

  Force the administrator to change the credential upon installation.

  Skuteczność: High

• Installation, Operation

  The product administrator could change the defaults upon installation or during operation.

  Skuteczność: Moderate

Przykłady podatności

• CVE-2018-3825 cloud cluster management product has a default master encryption key
• CVE-2016-1561 backup storage product has a default SSH public key in the authorized_keys file, allowing root access
• CVE-2010-2306 Intrusion Detection System (IDS) uses the same static, private SSL keys for multiple devices and installations, allowing decryption of SSL traffic

Słabość nadrzędna

• CWE-1392 Use of Default Credentials

Kiedy powstaje

• Architecture and Design

Dotyczy

Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Not Technology-Specific