708
CAPEC-ID Attack Pattern Name
476 Signature Spoofing by Misrepresentation
667 Bluetooth Impersonation AttackS (BIAS)
References
[REF-62]Mark Dowd, John McDonald and Justin Schuh. "The Art of Software Security
Assessment". 1st Edition. 2006. Addison Wesley.
CWE-291: Reliance on IP Address for Authentication
Weakness ID : 291
Structure : Simple
Abstraction : Variant
Description
The product uses an IP address for authentication.
Extended Description
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.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 471 Modification of Assumed-Immutable Data (MAID) 1121
ChildOf 923 Improper Restriction of Communication Channel to Intended
Endpoints