Reliance on IP Address for Authentication

Opis

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.

Skutki

• Access Control, Non-Repudiation

  Hide Activities; Gain Privileges or Assume Identity

  Malicious users can fake authentication information, impersonating any IP address.

Zapobieganie

• Architecture and Design

  Use other means of identity verification that cannot be simply spoofed. Possibilities include a username/password or certificate.

Przykłady podatności

• CVE-2022-30319 S-bus functionality in a home automation product performs access control using an IP allowlist, which can be bypassed by a forged IP address.

Słabość nadrzędna

• CWE-290 Authentication Bypass by Spoofing
• CWE-923 Improper Restriction of Communication Channel to Intended Endpoints

Kiedy powstaje

• Architecture and Design — COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.

Dotyczy

Not Language-Specific

Źródła

1. The CLASP Application Security Process — Secure Software, Inc., 2005
2. IP address spoofing — Wikipedia, 2006