CWE-300: Channel Accessible by Non-Endpoint | Codefreex Skip to content

Security weakness

CWE-300 Channel Accessible by Non-Endpoint

A class-level weakness that can lead to private data exposed, data, pages or code changed and accounts and admin areas exposed. Here is what it is, what it can cost you and how to close it.

  • Senior security engineers
  • 540+ projects delivered
  • Reply within one business day

Quick answer

What is CWE-300?

Channel Accessible by Non-Endpoint: 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.

Business impact

What CWE-300 could cost your business

MITRE documents what this weakness can do. Here is what that means for a website, store or app.

Confidentiality

Private data exposed

Customer records, credentials, orders or internal files can be read by people who should never see them.

  • Read Application Data
  • Modify Application Data
  • Gain Privileges or Assume Identity

Integrity

Data, pages or code changed

Prices, orders, content or the code your site runs can be altered without your approval.

  • Read Application Data
  • Modify Application Data
  • Gain Privileges or Assume Identity

Access Control

Accounts and admin areas exposed

Logins and permission checks can be bypassed, putting admin and customer accounts at risk.

  • Read Application Data
  • Modify Application Data
  • Gain Privileges or Assume Identity

Free security check

Is CWE-300 hiding in your site?

A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.

Official definition

How MITRE defines CWE-300

Channel Accessible by Non-Endpoint

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.

Also known as: Adversary-in-the-Middle / AITM, Attacker-in-the-Middle / AITM, Man-in-the-Middle / MITM, Person-in-the-Middle / PITM, Monkey-in-the-Middle, Monster-in-the-Middle, Manipulator-in-the-Middle, On-path attack

Weakness ID
CWE-300
Type
Class
Status
Draft
Introduced during
Architecture and Design

Prevention

How to fix CWE-300, phase by phase

Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.

  1. 01

    Architecture and Design

    • Adhere to the principle of complete mediation.
  2. 02

    Implementation

    • 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. Always fully authenticate both ends of any communications channel.
    • 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.

Detection and evidence

How CWE-300 is found, and where it has hit

The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.

How it is detected

  • Automated Dynamic AnalysisSome tools can act as proxy servers that allow the tester to intercept packets or messages, inspect them, and modify them before sending them to the destination in order to see if the modified packets are still accepted by the receiving component.
  • Automated Dynamic AnalysisDynamic Application Security Testing (DAST) tools can be used to detect network traffic without encryption and/or verification. The affected protocol may be subject to Adversary-in-the-Middle attacks. Some tools act as proxy servers that allow the tester to inspect and modify packets/messages to see.
  • Automated Static AnalysisAutomated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then.

Real vulnerabilities it caused

  • CVE-2014-1266Chain: 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) ->.

How we fix it

From finding to fixed: how Codefreex closes CWE-300

  1. 01

    Scan and confirm

    We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.

  2. 02

    Fix at the source

    We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.

  3. 03

    Verify the fix

    We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.

  4. 04

    Keep it fixed

    Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.

Related weaknesses

FAQ

CWE-300: FAQs

Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.

What is CWE-300?

CWE-300, “Channel Accessible by Non-Endpoint”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. 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.

How serious is CWE-300?

It can affect confidentiality, integrity, access control, with impacts such as read application data, modify application data, gain privileges or assume identity. The real risk depends on where the weakness sits and what data or functions it exposes.

How do you prevent CWE-300?

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. Always fully authenticate both ends of any communications channel. Adhere to the principle of complete mediation.

Can Codefreex check my site for CWE-300?

Yes. A senior engineer reviews your site, store or app for CWE-300 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.

Free security check

Find out if CWE-300 affects your site

Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.

  • A senior strategist reviews your request, not a sales bot
  • Clear scope, timeline and estimate within one business day
  • Free 30-minute discovery call, no obligation
  • NDA available on request

Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.