CWE-5: J2EE Misconfiguration: Data Transmission Without Encryption
Information sent over a network can be compromised while in transit. An attacker may be able to read or modify the contents if the data are sent in plaintext or are weakly encrypted.
Browse cwe in system configuration with official CWE context and Glexia analysis.
Search And Filters
Showing 46 of 46 CWE records.
Information sent over a network can be compromised while in transit. An attacker may be able to read or modify the contents if the data are sent in plaintext or are weakly encrypted.
The default error page of a web application should not display sensitive information about the product.
If elevated access rights are assigned to EJB methods, then an attacker can take advantage of the permissions to exploit the product.
Debugging messages help attackers learn about the system and plan a form of attack.
An ASP .NET application must enable custom error pages in order to prevent attackers from mining information from the framework's built-in responses.
The product contains a protection mechanism that restricts access to a long filename on a Windows operating system, but it does not properly restrict access to the equivalent short "8.3" filename.
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
The product generates an error message that includes sensitive information about its environment, users, or associated data.
The product performs an operation that triggers an external diagnostic or error message that is not directly generated or controlled by the product, such as an error generated by the programming language interpreter that a software application uses. The error can contain sensitive system information.
The product stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties.
The product stores sensitive data under the FTP server root with insufficient access control, which might make it accessible to untrusted parties.
The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses.
Using an empty string as a password is insecure.
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
The product, by default, initializes an internal variable with an insecure or less secure value than is possible.
Login pages do not use adequate measures to protect the user name and password while they are in transit from the client to the server.
The product stores a CVS, git, or other repository in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.
The product generates a core dump file in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.
The product stores access control list files in a directory or other container that is accessible to actors outside of the intended control sphere.
The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information.
Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.
If an include file source is accessible, the file can contain usernames and passwords, as well as sensitive information pertaining to the application and system.
The product inappropriately exposes a directory listing with an index of all the resources located inside of the directory.
Certain conditions, such as network failure, will cause a server error message to be displayed.
The product makes files or directories accessible to unauthorized actors, even though they should not be.
A possible shell file exists in /cgi-bin/ or other accessible directories. This is extremely dangerous and can be used by an attacker to execute commands on the web server.
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
An ActiveX control is intended for use in a web browser, but it exposes dangerous methods that perform actions that are outside of the browser's security model (e.g. the zone or domain).
An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.
The server contains a protection mechanism that assumes that any URI that is accessed using HTTP GET will not cause a state change to the associated resource. This might allow attackers to bypass intended access restrictions and conduct resource modification and deletion attacks, since some applications allow GET to modify state.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.
The bus controller enables bits in the fabric end-point to allow responder devices to control transactions on the fabric.
The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely.
The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.
A processor event may allow transient operations to access architecturally restricted data (for example, in another address space) in a shared microarchitectural structure (for example, a CPU cache), potentially exposing the data over a covert channel.
Shared microarchitectural predictor state may allow code to influence transient execution across a hardware boundary, potentially exposing data that is accessible beyond the boundary over a covert channel.
The product uses externally-provided data to build prompts provided to large language models (LLMs), but the way these prompts are constructed causes the LLM to fail to distinguish between user-supplied inputs and developer provided system directives.
The product has a component that relies on a generative AI/ML model configured with inference parameters that produce an unacceptably high rate of erroneous or unexpected outputs.