CAS-003 · Question #849
A developer is concerned about input validation for a newly created shopping-cart application, which will be released soon on a popular website. Customers were previously able to manipulate the…
The correct answer is B. Dynamic analysis. Dynamic analysis tests the live running application with real and crafted inputs, making it the most efficient method to confirm whether an input validation flaw in the shopping cart can still be exploited.
Question
A developer is concerned about input validation for a newly created shopping-cart application, which will be released soon on a popular website. Customers were previously able to manipulate the shopping cart so they could receive multiple items while only paying for one item. This resulted in large losses. Which of the following would be the MOST efficient way to test the shopping cart and address the developer’s concerns?
Options
- ALog analysis
- BDynamic analysis
- CVulnerability assessment
- DGray-box testing
- EManual code review
How the community answered
(54 responses)- A9% (5)
- B81% (44)
- C2% (1)
- D6% (3)
- E2% (1)
Why each option
Dynamic analysis tests the live running application with real and crafted inputs, making it the most efficient method to confirm whether an input validation flaw in the shopping cart can still be exploited.
Log analysis reviews historical event records and cannot proactively test whether an input validation vulnerability still exists in the updated application.
Dynamic analysis executes the application and actively probes input fields, hidden form values, and API parameters with crafted payloads while the application is running, directly revealing how runtime input validation behaves. For a previously exploited cart manipulation vulnerability, dynamic analysis tools can reproduce the exact attack conditions in real time, confirming whether the fix is effective without requiring a manual review of the entire codebase.
A vulnerability assessment is a broader process that encompasses multiple techniques including dynamic analysis; it is less targeted and therefore less efficient than directly running dynamic analysis against a known specific flaw.
Gray-box testing describes the tester's level of prior knowledge about the system and is a testing methodology classification, not a specific technique that provides efficiency advantages over dynamic analysis for this scenario.
Manual code review requires reading source code line by line to trace logic, which is time-consuming and indirect compared to running the application and observing actual input handling behavior in real time.
Concept tested: Dynamic analysis for runtime input validation testing
Source: https://owasp.org/www-community/Fuzzing
Topics
Community Discussion
No community discussion yet for this question.