Burp Extension Settings

Menu item After installing and loading the extension, there should be a menu item called BeanStack. You can open the settings from that menu.


Enable Lookups

Default: enabled

This toggles whether the extension is currently active, so that you do not have to unload or remove it to temporarily disable it.


Default: none

This text field contains your API key, if any. For the benefits of an API key, see the introduction page. Your key should look something like 2wiEUvnVU-lJhbgJz5B_OdJB.

API key field

Blacklisted Class Prefixes

Default: empty

This is a comma-separated list of strings that will be matched anywhere in a stack trace line.

To avoid submitting confidential information, it is possible to blacklist class prefixes. For example, a trace might contain lines like these:


While it is possible to submit hashed stack traces to avoid revealing their contents, we might theoretically (and illegally, as it is not in our privacy policy) brute force the hashes. To address the concern, you can choose to avoid sending certain names altogether. To remove any classes containing com.customerName. and net.customerName., configure the following value:


Note that if you omit the trailing dots, i.e. com.customerName,net.customerName, it would also match a line such as:


Hash traces before submission

Default: disabled
Note: This feature requires an API key.

When enabled, the Burp extension hashes the stack trace in parts before submitting it to the API. For example, the following trace:


Would be hashed into something like this:


It can still work because we hashed the entries in our database with the same algorithm, so we can match them. We cannot learn the contents of any part that is not already in our database.

Create an Issue for Each CVE

Default: disabled
Note: CVEs are only shown when you use an API key.

This toggles whether the extension creates an issue for each CVE it finds. For example, if two products are identified in a stack trace and each have two CVEs with varying CVSS scores, the default is to log one issue for the URL with the CVEs listed. The issue severity depends on the highest CVSS score (because, presumably, you can choose to exploit the most severe one). When enabling this setting, it will instead log four issues for that stack trace: one for each CVE found. The issues will then have appropriate severities in Burp.

One major downside is that there is no deduplication implemented: every time the CVE is encountered, it will log a new issue. It may therefore create a large number of issues, depending on the number of CVEs found in a stack trace.

Response Size Limit (RAM)

Default: 25 MiB
It is not generally needed to change this setting.

To prevent excessive RAM usage, the extension will process only the first and last limit/2 bytes (by default, the first 12.5 and last 12.5MiB). The limit is conservative, considering that Burp Suite and other extensions may already be using a lot of RAM for large HTTP responses and that responses with stack traces do not often exceed a few megabytes, and those that do are likely to have them near the end where the response-generating script crashed.

Print Debug Messages

Default: disabled
It is not generally needed to change this setting.

This toggles whether messages are logged to standard out. These messages can be viewed in the terminal from which Burp Suite was launched, if any.

Log Duplicates

Default: disabled
It is not generally needed to change this setting.

This toggles whether the extension avoids creating duplicate issues. It does not log an issue if it already exists for the same URL and with the same contents. It will log the same information again for a new URL if it was found there as well, or log new information for the same URL if a different stack trace was found (or if the server's database has been updated in the meantime and the response now contains new information).

Issue Title

Default: Stack Trace Fingerprint Found
It is not generally needed to change this setting.

This setting can be used to customize how BeanStack issues appear in the list.


Default: https://beanstack.io/api/
It is not generally needed to change this setting.

In case the API URL needs to be changed, for example to pass a corporate proxy, this setting can be used. Note that a trailing slash is automatically appended.