Kingdom: API Abuse

An API is a contract between a caller and a callee. The most common forms of API abuse are caused by the caller failing to honor its end of this contract. For example, if a program fails to call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller abuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated.

File Disclosure: Spring Webflow

Java/JSP

Abstract

Constructing a server-side redirect path with user input could allow an attacker to download application binaries (including application classes or jar files) or view arbitrary files within protected directories.

Explanation

In Spring Webflow, a view resolver is used to translate a view name into an actual rendering technology. Typically a view resolver will limit the type and location of the files using prefixes and suffixes. However, using request parameters specify the view name allows this mechanism to be circumvented.
Example 1: The following Spring Webflow configurations uses request parameters to specify the view name.


<webflow:end-state id="finalStep" view="${requestParameters.url}"/>
<webflow:view-state id="showView" view="${requestParameters.test}">

The default Spring Webflow view resolver is intended to only allow jsp files in "/WEB-INF/views/" to be resolved.



<bean class="org.springframework.web.servlet.view.
               InternalResourceViewResolver">
    <property name="prefix" value="/WEB-INF/views/" />
    <property name="suffix" value=".jsp" />
</bean>

An attacker could use the following URL to view the applicationContext.xml file: "http://www.yourcorp.com/webApp/logic?url=../applicationContext.xml;x="
The InternalResourceViewResolver will take the prefix it is configured with then concatenate the value passed in the view attribute and finally add the suffix.
The resulting relative URL, "/WEB-INF/views/../applicationContext.xml;x=.jsp" is passed to the server-side request dispatcher. The semicolon allows the attacker to convert the ".jsp" suffix into a path parameter. This attack can be used to disclose any file under the web app root.

References

[1] Ryan Berg and Dinis Cruz Two Security Vulnerabilities in the Spring Framework's MVC

[2] Seth Ladd Expert Spring MVC and Web Flow

[3] Standards Mapping - Common Weakness Enumeration CWE ID 552

[4] Standards Mapping - Common Weakness Enumeration Top 25 2024 [12] CWE ID 020

[5] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-002754

[6] Standards Mapping - General Data Protection Regulation (GDPR) Access Violation

[7] Standards Mapping - NIST Special Publication 800-53 Revision 4 SI-10 Information Input Validation (P1)

[8] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-10 Information Input Validation

[9] Standards Mapping - OWASP API 2023 API1 Broken Object Level Authorization

[10] Standards Mapping - OWASP Application Security Verification Standard 4.0 1.12.1 Secure File Upload Architectural Requirements (L2 L3), 12.5.1 File Download Requirements (L1 L2 L3)

[11] Standards Mapping - OWASP Mobile 2014 M1 Weak Server Side Controls

[12] Standards Mapping - OWASP Top 10 2004 A1 Unvalidated Input

[13] Standards Mapping - OWASP Top 10 2007 A4 Insecure Direct Object Reference

[14] Standards Mapping - OWASP Top 10 2010 A4 Insecure Direct Object References

[15] Standards Mapping - OWASP Top 10 2013 A4 Insecure Direct Object References

[16] Standards Mapping - OWASP Top 10 2017 A5 Broken Access Control

[17] Standards Mapping - OWASP Top 10 2021 A01 Broken Access Control

[18] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.1

[19] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.5.4

[20] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.8

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.8

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.8

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.8

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.8

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 6.2.4

[27] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 5.4 - Authentication and Access Control

[28] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 5.4 - Authentication and Access Control

[29] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 5.4 - Authentication and Access Control, Control Objective C.2.3 - Web Software Access Controls

[30] Standards Mapping - SANS Top 25 2009 Risky Resource Management - CWE ID 073

[31] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002560 CAT I

[32] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002560 CAT I

[33] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002560 CAT I

[34] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002560 CAT I

[35] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002560 CAT I

[36] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002560 CAT I

[37] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002560 CAT I

[38] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002560 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002560 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002560 CAT I

[41] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002560 CAT I

[42] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002560 CAT I

[43] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002560 CAT I

[44] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002560 CAT I

[45] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002560 CAT I

[46] Standards Mapping - Web Application Security Consortium Version 2.00 URL Redirector Abuse (WASC-38)

desc.configuration.java.file_disclosure_spring_webflow