The Local Exploit Suggester is a post-exploitation module that you can use to check a system for local vulnerabilities. It performs local exploit checks; it does not actually run any exploits, which is useful because this means you to scan a system without being intrusive. In addition to being stealthy, it's a time saver. You don't have to manually search for local exploits that will work; it'll show you which exploits the target is vulnerable to based on the system's platform and architecture.
* **SHOWDESCRIPTION** - Set this option to true to see more details about each exploit.
* **ValidateArch** - This option lets us toggle whether or not a mismatch in session and module architecture should be validated or ignored.
* **ValidatePlatform** - This option lets us toggle whether or not a mismatch in session and module platform should be validated or ignored.
* **ValidateMeterpreterCommands** - This option lets us toggle whether or not Meterpreter commands that are missing from the current Meterpreter implementation should be validated or ignored.
* **Colors** - Similar to the option used for `HttpTrace`. This lets us change the colors used to show valid, invalid and ignored options or incompatibilities. Unsetting this option results in no colored output.
When the Local Exploit Suggester runs, it displays a list of local exploits that the target may be vulnerable to, and it tells the user the likelihood of exploitation.
Furthermore, with the `Verbose` option turned on, a table is printed showing modules that were not considered as valid for the current session, and gives reasons as to why.
It provides a list of modules that did not have their `check` method executed, and provides information as to why a module is not compatible with the current session.
Note: In the table above, the session architecture is reported as `x64`. However, it is not considered as 'incompatible' as the `ValidateArch=false` option was used.
When the above is output to a terminal, the incompatibilities for a specific module (e.g. architecture or platform mismatch) are output in a different color if enabled with the `Color` datastore option.