Ferret is a simple wrapper for the Sentry PHP and JavaScript SDKs. It will catch all PHP errors, as well as JavaScript errors if the option is switched on. It utilizes the legacy PHP library by Sentry intentionally, in an effort to maximize compatibility. The newest SDK requires PHP^7.1 whereas the legacy requires minimum of 5.6
There are four settings that you can adjust.
- The
DSN– Your DSN key, this is required Project ID– The project key, this is also requiredEnable JavaScript Logging– Enable logging of JavaScript errorsIgnore WP Core Errors– Prevent sending events to Sentry that originate from WordPress core (wp-admin, wp-includes)Debug Environment– Switch the Sentry environment toDebug, turning this off puts the environment toProduction
All three are accessible on the plugin settings page located in the Settings -> Ferret Settings page.
In the future we will add the ability to selectively ignore specific themes or plugins in a convenient way. We would also like to expose an internal API that can be used by other plugins/themes to capture errors or add context.
CVE History
| CVE | Affected | Published | CVSS v3 | CVSS v2 |
|---|---|---|---|---|
| < 2.0.0, = 2.0.0 | 8.1 HIGH | — | ||
Ferret is a declarative system for working with web data. Prior to 2.0.0-alpha.4, a path traversal vulnerability in Ferret's IO::FS::WRITE standard library function allows a malicious website to write arbitrary files to the filesystem of the machine running Ferret. When an operator scrapes a website that returns filenames containing ../ sequences, and uses those filenames to construct output paths (a standard scraping pattern), the attacker controls both the destination path and the file content. This can lead to remote code execution via cron jobs, SSH authorized_keys, shell profiles, or web shells. This vulnerability is fixed in 2.0.0-alpha.4. | ||||