Description
The software protects a primary channel, but it does not use the same level of protection for an alternate channel.
Modes of Introduction:
– Architecture and Design
Related Weaknesses
Consequences
Access Control: Gain Privileges or Assume Identity, Bypass Protection Mechanism
Potential Mitigations
Phase: Architecture and Design
Description:
Identify all alternate channels and use the same protection mechanisms that are used for the primary channels.
CVE References
- CVE-2002-0567
- DB server assumes that local clients have performed authentication, allowing attacker to directly connect to a process to load libraries and execute commands; a socket interface also exists (another alternate channel), so attack can be remote.
- CVE-2002-1578
- Product does not restrict access to underlying database, so attacker can bypass restrictions by directly querying the database.
- CVE-2003-1035
- User can avoid lockouts by using an API instead of the GUI to conduct brute force password guessing.
- CVE-2002-1863
- FTP service can not be disabled even when other access controls would require it.
- CVE-2002-0066
- Windows named pipe created without authentication/access control, allowing configuration modification.
- CVE-2004-1461
- Router management interface spawns a separate TCP connection after authentication, allowing hijacking by attacker coming from the same IP address.
More Stories
The Most Dangerous Vulnerabilities in Apache Tomcat and How to Protect Against Them
Apache Tomcat is an open-source web server and servlet container that is widely used in enterprise environments to run Java...
ZDI-CAN-18333: A Critical Zero-Day Vulnerability in Microsoft Windows
Zero-day vulnerabilities are a serious threat to cybersecurity, as they can be exploited by malicious actors to gain unauthorized access...
CWE-669 – Incorrect Resource Transfer Between Spheres
Description The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere,...
CWE-67 – Improper Handling of Windows Device Names
Description The software constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a...
CWE-670 – Always-Incorrect Control Flow Implementation
Description The code contains a control flow path that does not reflect the algorithm that the path is intended to...
CWE-671 – Lack of Administrator Control over Security
Description The product uses security features in a way that prevents the product's administrator from tailoring security settings to reflect...