CWE-420 · Słabość
Unprotected Alternate Channel
- Abstrakcja
- Bazowa
- Status
- Szkic
- Dodano
- 19 lipca 2006
- Ostatnia zmiana
- 11 grudnia 2025
Opis
The product protects a primary channel, but it does not use the same level of protection for an alternate channel.
Skutki
Access Control
Gain Privileges or Assume Identity; Bypass Protection Mechanism
Zapobieganie
Architecture and Design
Identify all alternate channels and use the same protection mechanisms that are used for the primary channels.
Przykłady podatności
- CVE-2020-8004 When the internal flash is protected by blocking access on the Data Bus (DBUS), it can still be indirectly accessed through the Instruction Bus (IBUS).
- 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.
Słabość nadrzędna
Słabości podrzędne
Kiedy powstaje
- Architecture and Design — OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.
- Implementation
- Operation
Dotyczy
Not Language-Specific
Uwagi
This can be primary to authentication errors, and resultant from unhandled error conditions.
Wpis z katalogu CWE 4.20.