CWE-322 Base Draft High likelihood

Key Exchange without Entity Authentication

This vulnerability occurs when a system establishes a cryptographic key with another party without first confirming that party's true identity.

Definition

What is CWE-322?

This vulnerability occurs when a system establishes a cryptographic key with another party without first confirming that party's true identity.
While a key exchange can encrypt the communication channel between two systems, it does not automatically verify who is on the other end. If you skip the authentication step, you might be securely talking to an imposter. This is like having a perfectly sealed, private conversation with someone who is pretending to be your bank—the privacy is intact, but you've trusted the wrong entity. In a typical attack, a client application mistakenly connects to a malicious server masquerading as a trusted one. If the client proceeds without checking the server's credentials, the fake server can steal user login details, intercept sensitive data, or relay information to the real server while monitoring the entire session. The attacker essentially sits in the middle, with both parties unaware their secure channel has been compromised from the start.
Real-world impact

Real-world CVEs caused by CWE-322

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable pseudo

MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.

Vulnerable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Secure code example

Secure pseudo

Secure pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-322

  • Architecture and Design Ensure that proper authentication is included in the system design.
  • Implementation Understand and properly implement all checks necessary to ensure the identity of entities involved in encrypted communications.
Detection signals

How to detect CWE-322

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-322 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-322?

This vulnerability occurs when a system establishes a cryptographic key with another party without first confirming that party's true identity.

How serious is CWE-322?

MITRE rates the likelihood of exploit as High — this weakness is actively exploited in the wild and should be prioritized for remediation.

What languages or platforms are affected by CWE-322?

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-322?

Ensure that proper authentication is included in the system design. Understand and properly implement all checks necessary to ensure the identity of entities involved in encrypted communications.

How does Plexicus detect and fix CWE-322?

Plexicus's SAST engine matches the data-flow signature for CWE-322 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-322?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/322.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-322

CWE-306 Parent

Missing Authentication for Critical Function

This vulnerability occurs when a software feature that performs a sensitive action or uses significant system resources does not verify…

CWE-288 Sibling

Authentication Bypass Using an Alternate Path or Channel

This vulnerability occurs when a system has a primary login requirement, but attackers can find an unprotected backdoor or alternative…

CWE-923 Can precede

Improper Restriction of Communication Channel to Intended Endpoints

This vulnerability occurs when a system opens a communication channel for a sensitive task but fails to properly verify that it's actually…

CWE-295 Peer

Improper Certificate Validation

This vulnerability occurs when an application fails to properly verify the authenticity of a digital certificate, or performs the…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.

Get started free Book a demo