14:I[5228,["3385","static/chunks/3385-b76bb0d389ecb847.js","5753","static/chunks/5753-3df3dcd374d56bde.js","4462","static/chunks/4462-2f1547025558c923.js","1766","static/chunks/1766-e0a00c1dbb04d867.js","2122","static/chunks/2122-0aa89565809d0f14.js","8198","static/chunks/8198-02259efa89977c06.js","8058","static/chunks/8058-250b9e00e45a105b.js","2476","static/chunks/2476-39b31f73cd0731dd.js","4317","static/chunks/4317-05b07ec5dd2dfc17.js","8279","static/chunks/8279-51bfd849e487548c.js","9420","static/chunks/9420-af651d52266219df.js","1050","static/chunks/1050-c17118e9648df02f.js","9259","static/chunks/9259-b80e9833ae7b100c.js","7670","static/chunks/7670-77670847a8e0a1cb.js","1768","static/chunks/app/knowledgebases/%5BattackType%5D/%5Bid%5D/page-884b6d4b6fea536c.js"],"default"] 15:T512,The product uses weak credentials (such as a default key or hard-coded password) that can be calculated, derived, reused, or guessed by an attacker. -------------

By design, authentication protocols try to ensure that attackers must perform brute force attacks if they do not know the credentials such as a key or password. However, when these credentials are easily predictable or even fixed (as with default or hard-coded passwords and keys), then the attacker can defeat the mechanism without relying on brute force.

Credentials may be weak for different reasons, such as:

Hard-coded (i.e., static and unchangeable by the administrator)
Default (i.e., the same static value across different deployments/installations, but able to be changed by the administrator)
Predictable (i.e., generated in a way that produces unique credentials across deployments/installations, but can still be guessed with reasonable efficiency)
Previously Compromised (i.e., "leaked" credentials that were published as part of a data breach)

Even if a new, unique credential is intended to be generated for each product installation, if the generation is predictable, then that may also simplify guessing attacks.

Use of Weak Credentials