Description
The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.
Potential Impact
Confidentiality, Integrity, Availability, Access Control
Read Application Data, Modify Application Data, Execute Unauthorized Code or Commands, Gain Privileges or Assume Identity
Demonstrative Examples
http://somesite.com/someapplication/admin.jspMitigations & Prevention
Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files.
Consider using MVC based frameworks such as Struts.
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2022-29238 | Access-control setting in web-based document collaboration tool is not properly implemented by the code, which prevents listing hidden directories but does not prevent direct requests to files in thos |
| CVE-2004-2144 | Bypass authentication via direct request. |
| CVE-2005-1892 | Infinite loop or infoleak triggered by direct requests. |
| CVE-2004-2257 | Bypass auth/auth via direct request. |
| CVE-2005-1688 | Direct request leads to infoleak by error. |
| CVE-2005-1697 | Direct request leads to infoleak by error. |
| CVE-2005-1698 | Direct request leads to infoleak by error. |
| CVE-2005-1685 | Authentication bypass via direct request. |
| CVE-2005-1827 | Authentication bypass via direct request. |
| CVE-2005-1654 | Authorization bypass using direct request. |
| CVE-2005-1668 | Access privileged functionality using direct request. |
| CVE-2002-1798 | Upload arbitrary files via direct request. |
Related Weaknesses
Taxonomy Mappings
- PLOVER: — Direct Request aka 'Forced Browsing'
- OWASP Top Ten 2007: A10 — Failure to Restrict URL Access
- OWASP Top Ten 2004: A1 — Unvalidated Input
- OWASP Top Ten 2004: A2 — Broken Access Control
- WASC: 34 — Predictable Resource Location
- Software Fault Patterns: SFP30 — Missing endpoint authentication
Frequently Asked Questions
What is CWE-425?
CWE-425 (Direct Request ('Forced Browsing')) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.
How can CWE-425 be exploited?
Attackers can exploit CWE-425 (Direct Request ('Forced Browsing')) to read application data, modify application data, execute unauthorized code or commands, gain privileges or assume identity. This weakness is typically introduced during the Implementation, Operation phase of software development.
How do I prevent CWE-425?
Key mitigations include: Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files.
What is the severity of CWE-425?
CWE-425 is classified as a Base-level weakness (Medium abstraction). It has been observed in 12 real-world CVEs.