ClassDraft

CWE-300Channel Accessible by Non-Endpoint

Category: other

Description

The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint. In order to establish secure communication between two parties, it is often important to adequately verify the identity of entities at each end of the communication channel. Inadequate or inconsistent verification may result in insufficient or incorrect identification of either communicating entity. This can have negative consequences such as misplaced trust in the entity at the other end of the channel. An attacker can leverage this by interposing between the communicating entities and masquerading as the original entity. In the absence of sufficient verification of identity, such an attacker can eavesdrop and potentially modify the communication between the original entities.

Common consequences· 1

  • Confidentiality / Integrity / Access Control — Read Application Data, Modify Application Data, Gain Privileges or Assume Identity
    An attacker could pose as one of the entities and read or possibly modify the communication.

Potential mitigations· 3

  • [Implementation]Always fully authenticate both ends of any communications channel.
  • [Architecture and Design]Adhere to the principle of complete mediation.
  • [Implementation]A certificate binds an identity to a cryptographic key to authenticate a communicating party. Often, the certificate takes the encrypted form of the hash of the identity of the subject, the public key, and information such as time of issue or expiration using the issuer's private key. The certificate can be validated by deciphering the certificate with the issuer's public key. See also X.509 certificate signature chains and the PGP certification structure.

Related CAPEC attack patterns· 9

CAPEC-466CAPEC-57CAPEC-589CAPEC-590CAPEC-612CAPEC-613CAPEC-615CAPEC-662CAPEC-94

References

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

Exploits (incoming)9

TypeTargetConfidenceTier
AttackPatternEvil Twin Wi-Fi Attackcapec-615100%live
AttackPatternAdversary in the Middle (AiTM)capec-94100%live
AttackPatternAdversary in the Browser (AiTB)capec-662100%live
AttackPatternUtilizing REST's Trust in the System Resource to Obtain Sensitive Datacapec-57100%live
AttackPatternDNS Blockingcapec-589100%live
AttackPatternWiFi MAC Address Trackingcapec-612100%live
AttackPatternLeveraging Active Adversary in the Middle Attacks to Bypass Same Origin Policycapec-466100%live
AttackPatternWiFi SSID Trackingcapec-613100%live
AttackPatternIP Address Blockingcapec-590100%live

(incoming)1

TypeTargetConfidenceTier
VulnerabilityCVE-2025-31214cve-2025-312140%live

Related by meaning· 6

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

CWE
Improper Restriction of Communication Channel to Intended Endpoints
CWE
Improper Enforcement of Message Integrity During Transmission in a Communication Channel
CWE
Improper Verification of Source of a Communication Channel
CWE
Key Exchange without Entity Authentication
CWE
Race Condition During Access to Alternate Channel
CWE
Unprotected Primary Channel
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.