10 lines
1.2 KiB
Plaintext
10 lines
1.2 KiB
Plaintext
|
Hardcoding IP addresses is security-sensitive. It has led in the past to the following vulnerabilities:
|
||
|
|
* http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5901[CVE-2006-5901]
|
||
|
|
* http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-3725[CVE-2005-3725]
|
||
|
|
|
||
|
|
Today's services have an ever-changing architecture due to their scaling and redundancy needs. It is a mistake to think that a service will always have the same IP address. When it does change, the hardcoded IP will have to be modified too. This will have an impact on the product development, delivery and deployment:
|
||
|
|
* The developers will have to do a rapid fix every time this happens, instead of having an operation team change a configuration file.
|
||
|
|
* It forces the same address to be used in every environment (dev, sys, qa, prod).
|
||
|
|
|
||
|
|
Last but not least it has an effect on application security. Attackers might be able to decompile the code and thereby discover a potentially sensitive address. They can perform a Denial of Service attack on the service at this address or spoof the IP address. Such an attack is always possible, but in the case of a hardcoded IP address the fix will be much slower, which will increase an attack's impact.
|