VariantIncomplete

CWE-291Reliance on IP Address for Authentication

Category: auth

Description

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.

Common consequences· 1

  • Access Control / Non-Repudiation — Hide Activities, Gain Privileges or Assume Identity
    Malicious users can fake authentication information, impersonating any IP address.

Potential mitigations· 1

  • [Architecture and Design]Use other means of identity verification that cannot be simply spoofed. Possibilities include a username/password or certificate.

Related CAPEC attack patterns· 1

CAPEC-4

References

  1. https://cwe.mitre.org/data/definitions/291.html

Exploits (incoming)1

TypeTargetConfidenceTier
AttackPatternUsing Alternative IP Address Encodingscapec-4100%live

(incoming)3

TypeTargetConfidenceTier
VulnerabilityCVE-2025-34202cve-2025-342020%live
VulnerabilityCVE-2025-66602cve-2025-666020%live
VulnerabilityCVE-2026-4252cve-2026-42520%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Weak Authentication
CWE
Reliance on Reverse DNS Resolution for a Security-Critical Action
CWE
Use of Hard-coded Password
CWE
Use of Password Hash Instead of Password for Authentication
CWE
Use of Single-factor Authentication
CWE
Insufficiently Protected Credentials
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.