Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.
CWE-5 Variant Draft
J2EE Misconfiguration: Data Transmission Without Encryption
This vulnerability occurs when a J2EE application transmits sensitive data, like login credentials or session tokens, across a network without using strong encryption. Attackers monitoring the…
Definition
What is CWE-5?
This vulnerability occurs when a J2EE application transmits sensitive data, like login credentials or session tokens, across a network without using strong encryption. Attackers monitoring the network can easily intercept, read, or even alter this information if it's sent in plain text or protected by weak cryptographic methods.
In modern applications, data is constantly moving between clients, servers, and backend systems. When this communication isn't properly secured with protocols like TLS/SSL, it's akin to sending a confidential letter on a postcard—anyone handling it can read the contents. This exposes user data, authentication details, and business information to eavesdropping and manipulation during transit.
To prevent this, developers must ensure all sensitive communications are encrypted end-to-end. This means enforcing HTTPS for web traffic, using up-to-date TLS configurations, and avoiding custom or deprecated encryption protocols. Proper implementation acts as a secure tunnel, ensuring data confidentiality and integrity from the point it leaves the client until it reaches the intended server.
Real-world impact
Real-world CVEs caused by CWE-5
No public CVE references are linked to this CWE in MITRE's catalog yet.
How attackers exploit it
Step-by-step attacker path
- 1
Identify a code path that handles untrusted input without validation.
- 2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
- 3
Deliver the payload through a normal request and observe the application's reaction.
- 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.
// 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
// 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-5
- System Configuration The product configuration should ensure that SSL or an encryption mechanism of equivalent strength and vetted reputation is used for all access-controlled pages.
Detection signals
How to detect CWE-5
Run dynamic application security testing against the live endpoint.
Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.
Code review: flag any new code that handles input from this surface without using the validated framework helpers.
CWE-5
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Frequently asked questions What is CWE-5?
How serious is CWE-5?
What languages or platforms are affected by CWE-5?
How can I prevent CWE-5?
How does Plexicus detect and fix CWE-5?
Where can I learn more about CWE-5?
Frequently asked questions
What is CWE-5?
This vulnerability occurs when a J2EE application transmits sensitive data, like login credentials or session tokens, across a network without using strong encryption. Attackers monitoring the network can easily intercept, read, or even alter this information if it's sent in plain text or protected by weak cryptographic methods.
How serious is CWE-5?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-5?
MITRE lists the following affected platforms: Java.
How can I prevent CWE-5?
The product configuration should ensure that SSL or an encryption mechanism of equivalent strength and vetted reputation is used for all access-controlled pages.
How does Plexicus detect and fix CWE-5?
Plexicus's SAST engine matches the data-flow signature for CWE-5 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-5?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/5.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-5
CWE-319 Parent
Cleartext Transmission of Sensitive Information
This vulnerability occurs when an application sends sensitive data, such as passwords or personal information, over a network connection…
CWE-1428 Sibling
Reliance on HTTP instead of HTTPS
This vulnerability occurs when an application uses unencrypted HTTP connections instead of the secure HTTPS alternative, even when HTTPS…
CWE-614 Sibling
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
This vulnerability occurs when a web application transmits sensitive cookies over an HTTPS connection but fails to set the 'Secure'…
Resources
Further reading
- MITRE — official CWE-5 https://cwe.mitre.org/data/definitions/5.html
- Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors https://samate.nist.gov/SSATTM_Content/papers/Seven%20Pernicious%20Kingdoms%20-%20Taxonomy%20of%20Sw%20Security%20Errors%20-%20Tsipenyuk%20-%20Chess%20-%20McGraw.pdf
Ready to validate what matters?
Ready to validate what matters?
Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.