PAVINDAS / VAPT Report
Loading... reads All Articles

Penetration Test Report: Zero Bank

A rigorous web application vulnerability assessment of Zero Bank. Uncovering severe access control failures, unauthenticated administrative access, IDOR on customer accounts, CSRF financial transfers, and SQL injection flaws.

Section 01 // Target Scope

Target Information & Testing Details

Assessment Scope

• Application Name: Zero Bank
• Target URL: http://zero.webappsecurity.com/
• Tools Leveraged: Gobuster, Burp Suite Community Edition, Wappalyzer
• External Utility: CSRF Shark PoC Generator
• Methodology: Enumeration, Manual logic validation, Exploitation, and remediation reporting.

Section 02 // Finding 1

1. Broken Access Control & Sensitive Admin Exposure

Unauthenticated Administrative Interface & Logs Exposure
OWASP A01:2021 — Broken Access Control
Critical Severity

The administrative dashboard and system error logs are directly accessible without any authentication or authorization checks, exposing internal system telemetry and administrative controls.

Affected Endpoints /admin/, /errors/logs
Evidence #01 — Direct Admin Access Click to expand
Admin portal accessible without authentication
Figure 1: Accessing /admin/ directly reveals sensitive user controls without requiring login.
Evidence #02 — Sensitive Error Logs Click to expand
Exposed system logs
Figure 2: Exposed error logs on /errors/logs.
Section 03 // Finding 2

2. Default Credentials Exposure

Authentication Bypass via Exposed Default Credentials
OWASP A07:2021 — Identification & Authentication Failures
High Severity

The application discloses default administrative and user credentials directly through the login help documentation.

Disclosed Credentials
username:password
Evidence #03 — Login Help Disclosure Click to expand
Default credentials exposed in help
Figure 3: Help documentation disclosing valid authentication credentials.
Section 04 // Finding 3

3. Insecure Direct Object Reference (IDOR)

Horizontal Privilege Escalation on Account Activity
OWASP A01:2021 — Broken Access Control
Critical Severity

The application does not validate whether the authenticated user owns the requested account object, allowing any customer to view the financial transaction history of arbitrary accounts by altering query parameters.

IDOR Parameter Tampering
GET /account-activity.html?accountId=1 → Tampered to: accountId=2
Evidence #04 — Account IDOR Proof Click to expand
Accessing another user's bank transactions via IDOR
Figure 4: Modifying accountId exposes sensitive financial records of other users.
Section 05 // Finding 4

4. Cross-Site Request Forgery (CSRF) on Fund Transfer

Unauthorized Fund Transfers via CSRF
OWASP A01:2021 — Broken Access Control
Critical Severity

The fund transfer confirmation endpoint lacks anti-CSRF token verification and SameSite cookie restrictions, enabling attackers to force victims into transferring money.

HTML CSRF PoC Exploit
<!DOCTYPE html>
<html lang="en">
    <body>
        <h1>Form CSRF PoC</h1>
        <form method="POST" action="http://zero.webappsecurity.com/bank/transfer-funds-confirm.html">
            <input type="hidden" name="fromAccountId" value="1">
            <input type="hidden" name="toAccountId" value="1">
            <input type="hidden" name="amount" value="500">
            <input type="hidden" name="description" value="CSRF">
            <input type="submit" value="Submit Request">
        </form>
    </body>
</html>
Evidence #05 — CSRF Fraud Execution Click to expand
Executing CSRF attack to trigger fund transfer
Figure 5: Automated execution of fund transfer via cross-site request forgery.
Section 06 // Findings 5 & 6

5. Stored XSS & 6. SQL Injection

Stored Cross-Site Scripting (XSS) in Admin Panel
OWASP A03:2021 — Injection
High Severity

User input submitted through support or feedback functionality is stored without sanitization and executes in the context of the administrator panel.

Evidence #06 — Stored XSS Execution Click to expand
Stored XSS alert popup in admin portal
Figure 6: Stored XSS payload triggering inside the admin portal.
SQL Injection in Payee Parameter
OWASP A03:2021 — Injection
Critical Severity

The payeeId parameter fails to use parameterized queries, allowing SQL syntax injection to extract backend database records.

Evidence #07 — SQL Injection Validation Click to expand
SQL injection error and data extraction
Figure 7: SQL Injection proof in payeeId parameter.
Section 07 // Finding 7

7. Information Disclosure & Outdated Server Components

Outdated Apache Tomcat 7.0.70 with Known CVEs
OWASP A06:2021 — Vulnerable & Outdated Components
Medium Severity

Detailed server version banners expose Apache Tomcat 7.0.70, an end-of-life release subject to multiple publicly documented remote code execution and denial-of-service vulnerabilities.

Evidence #08 — Apache Tomcat 7.0.70 Exposure Click to expand
Server error banner disclosing Apache Tomcat 7.0.70
Figure 8: Server header revealing outdated Apache Tomcat 7.0.70.
Section 08 // Summary

Conclusion & Strategic Remediation

Identifying and remediating critical vulnerabilities such as Broken Access Control, IDOR, and SQL Injection is indispensable for financial web platforms. Implementing zero-trust authorization checks, parameterized queries, and anti-CSRF tokens must be prioritized.

Author's Note

Thank you for reading this VAPT assessment report on the Zero Bank application! I hope this walkthrough delivers practical insights into offensive testing methodologies and mitigation best practices. Best of luck on your hacking journey!

01. Target & Scope • 0%
Assessment Sections