The software contains a hard-coded password, which it uses for
					its own inbound authentication or for outbound communication to external
					components.A hard-coded password typically leads to a significant authentication
						failure that can be difficult for the system administrator to detect. Once
						detected, it can be difficult to fix, so the administrator may be forced
						into disabling the product entirely. There are two main variations:In the Inbound 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 software. If the password is ever discovered or published (a common
						occurrence on the Internet), then anybody with knowledge of this password
						can access the product. Finally, since all installations of the software
						will have the same password, even across different organizations, this
						enables massive attacks such as worms to take place.The Outbound variant applies to front-end systems that authenticate with a
						back-end service. The back-end service may require a fixed password which
						can be easily discovered. The programmer may simply hard-code those back-end
						credentials into the front-end software. Any user of that program may be
						able to extract the password. Client-side systems with hard-coded passwords
						pose even more of a threat, since the extraction of a password from a binary
						is usually very simple.