Grey-Box Security Test Tools CT-STE Practice Questions (Page 4)

Questions 16–20

1. 16foundation · easy

   When operating a grey-box fuzzer, what is a typical configuration step to improve test coverage?

   • AProviding valid seed inputs that the fuzzer can mutate to generate new test cases
   • BSetting the fuzzer to only test the login page
   • CDisabling all error handling to force crashes
   • DTurning off logging to improve performance
   Reveal Solution Discussion Select an answer first
2. 17expert · hard

   A grey-box fuzzer is testing a file parser. The fuzzer has found a crash, but the crash is not reproducible when the same input is run again. The tester has the source code and can rebuild. What is the most likely cause of the non-reproducible crash?

   • AThe crash depends on uninitialized memory or a race condition that is not deterministic
   • BThe fuzzer is generating inputs that are too large for the parser to handle
   • CThe fuzzer is not saving the exact input that caused the crash
   • DThe parser is correctly rejecting the input, and the crash is a false positive
   Reveal Solution Discussion Select an answer first
4. 18foundation · easy

   When prioritizing vulnerabilities found by grey-box tools, which factor is most important to consider?

   • AThe name of the tool that found the vulnerability
   • BThe number of lines of code affected by the vulnerability
   • CThe order in which the tool reported the findings
   • DThe severity of the vulnerability and its exploitability in the application's context
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   In grey-box security testing, the tester typically has:

   • ANo knowledge of the internal workings of the application, testing only through the user interface
   • BOnly the compiled binary and no documentation, requiring reverse engineering to understand behavior
   • CFull access to source code, architecture diagrams, and internal documentation
   • DPartial knowledge of the internal structure, such as some code snippets, API specifications, or database schemas
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   A security team must choose a grey-box tool to test a Java microservices application that uses Kafka for messaging and exposes REST endpoints. The team has the source code and CI/CD pipeline. They need to find both concurrency bugs and injection flaws, and they have a limited budget for commercial tools. Which tool selection best meets these requirements?

   • AIntegrate an open-source static analyzer (e.g., SpotBugs) into the CI pipeline and use an open-source REST API fuzzer for dynamic testing
   • BDeploy a network vulnerability scanner to test the Kafka and REST infrastructure
   • CPurchase a single commercial DAST tool that scans the REST endpoints
   • DUse only a commercial SAST tool and rely on manual code review for dynamic issues
   Reveal Solution Discussion Select an answer first