CWE-291: Reliance on IP Address for Authentication
The product uses an IP address for authentication.
IP addresses can be easily spoofed. Attackers can forge the source IP address of the packets they send, but response packets will return to the forged IP address. To see the response packets, the attacker has to sniff the traffic between the victim machine and the forged IP address. In order to accomplish the required sniffing, attackers typically attempt to locate themselves on the same subnet as the victim machine. Attackers may be able to circumvent this requirement by using source routing, but source routing is disabled across much of the Internet today. In summary, IP address verification can be a useful part of an authentication scheme, but it should not be the single factor required for authentication.
Consequences
- Access Control, Non-Repudiation: Hide Activities, Gain Privileges or Assume Identity
How to prevent it
- Architecture and Design: Use other means of identity verification that cannot be simply spoofed. Possibilities include a username/password or certificate.
Recent advisories
- GHSA-vvjh-f6p9-5vcf — OpenClaw Canvas Authentication Bypass Vulnerability
- GHSA-hx53-jchx-cr52 — Symfony2 improper IP based access control
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor