Weakness (CWE)
CWE-291: Reliance on IP Address for Authentication
The product uses an IP address for authentication.
How to prevent it (1 mitigation)
-
Architecture and Design
Use other means of identity verification that cannot be simply spoofed. Possibilities include a username/password or certificate. While IP address verification can be a useful part of an authentication scheme, but it should not be the single factor required for authentication.
Source: MITRE CWE-291
4 results · Clear filters · Feed
-
High 8.8
A session validation vulnerability has been identified in the SonicOS management interface, which in specific condition…
-
High 7.4
OpenClaw Canvas Authentication Bypass Vulnerability
OpenClaw Canvas Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of OpenClaw. Authentication is not required to exploit this vulnerability. The specific flaw exists within the i…
-
High 7.7
Insufficient Session Management in dormakaba access manager
Instead of typical session tokens or cookies, it is verified on a per-request basis if the originating IP address has once successfully logged in. As soon as an authentication request from a certain source IP is successful, the IP address is handled as authen…
-
High 8.7
Vasion Print (formerly PrinterLogic) Insecure Access to Docker Instances WAN
Vasion Print (formerly PrinterLogic) Virtual Appliance Host prior to 25.2.169 and Application prior to 25.2.1518 (VA and SaaS deployments) expose Docker internal networks in a way that allows an attacker on the same external L2 segment — or an attacker able t…