CWE-73: External Control of File Name or Path
The product allows user input to control or influence paths or file names that are used in filesystem operations.
Browse cwe in installation with official CWE context and Glexia analysis.
Search And Filters
Showing 18 of 18 CWE records.
The product allows user input to control or influence paths or file names that are used in filesystem operations.
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 appears to contain benign or useful functionality, but it also contains code that is hidden from normal operation that violates the intended security policy of the user or the system administrator.
Non-replicating malicious code only resides on the target system or product that is attacked; it does not attempt to spread to other systems.
Replicating malicious code, including viruses and worms, will attempt to attack other systems once it has successfully compromised the target system or the product.
A trapdoor is a hidden piece of code that responds to a special input, allowing its user access to resources without passing through the normal security enforcement mechanism.
The product contains code that is designed to disrupt the legitimate operation of the product (or its environment) when a certain time passes, or when a certain logical condition is met.
The product collects personally identifiable information about a human user or the user's activities, but the product accesses this information using other resources besides itself, and it does not require that user's explicit approval or direct input into the product.
Accessible test applications can pose a variety of security risks. Since developers or administrators rarely consider that someone besides themselves would even know about the existence of these applications, it is common for them to contain sensitive information or functions.
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 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 contains functionality that is not documented, not part of the specification, and not accessible through an interface or command sequence that is obvious to the product's users or administrators.
The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.
The product uses default passwords for potentially critical functionality.
The product uses a default cryptographic key for potentially critical functionality.
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.