Reliance on IP Address for Authentication
This vulnerability occurs when a system uses a client's IP address as the sole or primary method to verify their identity.
Relying solely on an IP address for authentication is a significant security risk because these addresses are not reliable proof of identity. Attackers can easily forge, or 'spoof,' the source IP address in the network packets they send. While this manipulation makes response packets return to the faked address, a determined attacker can intercept this return traffic, especially if they are on the same network segment as the target system. Therefore, an IP address should only ever be used as one component within a broader, multi-factor authentication strategy. It can provide a useful layer of context, such as for geolocation or anomaly detection, but it must be combined with stronger credentials like API keys, tokens, or certificates. Using it alone is equivalent to trusting a return address on an envelope as definitive proof of the sender's identity.
Impact: Hide ActivitiesGain Privileges or Assume Identity
Malicious users can fake authentication information, impersonating any IP address.
ID : DX-99
Both of these examples check if a request is from a trusted address before responding to the request.Code Example:
cCode Example:
javaHigh
- CLASP