Improper Restriction of Communication Channel to Intended Endpoints

Opis

The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint.

Attackers might be able to spoof the intended endpoint from a different system or process, thus gaining the same level of access as the intended endpoint.

While this issue frequently involves authentication between network-based clients and servers, other types of communication channels and endpoints can have this weakness.

Skutki

• Integrity, Confidentiality

  Gain Privileges or Assume Identity

  If an attacker can spoof the endpoint, the attacker gains all the privileges that were intended for the original endpoint.

Przykłady podatności

• CVE-2022-30319 S-bus functionality in a home automation product performs access control using an IP allowlist, which can be bypassed by a forged IP address.
• CVE-2022-22547 A troubleshooting tool exposes a web server on a random port between 9000-65535 that could be used for information gathering
• CVE-2022-4390 A WAN interface on a router has firewall restrictions enabled for IPv4, but it does not for IPv6, which is enabled by default
• CVE-2012-2292 Product has a Silverlight cross-domain policy that does not restrict access to another application, which allows remote attackers to bypass the Same Origin Policy.
• CVE-2012-5810 Mobile banking application does not verify hostname, leading to financial loss.
• CVE-2014-1266 Chain: incorrect "goto" in Apple SSL product bypasses certificate validation, allowing Adversary-in-the-Middle (AITM) attack (Apple "goto fail" bug). CWE-705 (Incorrect Control Flow Scoping) -> CWE-561 (Dead Code) -> CWE-295 (Improper Certificate Validation) -> CWE-393 (Return of Wrong Status Code) -> CWE-300 (Channel Accessible by Non-Endpoint). The code's whitespace indentation did not reflect the actual control flow (CWE-1114) and did not explicitly delimit the block (CWE-483), which could have made it more difficult for human code auditors to detect the vulnerability.
• CVE-2000-1218 DNS server can accept DNS updates from hosts that it did not query, leading to cache poisoning

Słabość nadrzędna

• CWE-284 Improper Access Control

Słabości podrzędne

• CWE-291 Reliance on IP Address for Authentication
• CWE-297 Improper Validation of Certificate with Host Mismatch
• CWE-300 Channel Accessible by Non-Endpoint
• CWE-419 Unprotected Primary Channel
• CWE-420 Unprotected Alternate Channel
• CWE-940 Improper Verification of Source of a Communication Channel
• CWE-941 Incorrectly Specified Destination in a Communication Channel
• CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains
• CWE-1275 Sensitive Cookie with Improper SameSite Attribute

Kiedy powstaje

• Architecture and Design — REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Dotyczy

Not Language-Specific, Not Technology-Specific, Web Based, Web Server