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:T48e,The product contains hard-coded credentials, such as a password or cryptographic key. -------------

There are two main variations:

Inbound: the product contains an authentication mechanism that checks the input credentials against a hard-coded set of credentials. In this variant, a default administration account is created, and a simple password is hard-coded into the product and associated with that account. This hard-coded password is the same for each installation of the product, and it usually cannot be changed or disabled by system administrators without manually modifying the program, or otherwise patching the product. It can also be difficult for the administrator to detect.
Outbound: the product connects to another system or component, and it contains hard-coded credentials for connecting to that component. This variant applies to front-end systems that authenticate with a back-end service. The back-end service may require a fixed password that can be easily discovered. The programmer may simply hard-code those back-end credentials into the front-end product.

Use of Hard-coded Credentials