Synopsis
Tenable Research discovered an issue in Ada.cx's Sentry configuration that allowed for blind server-side request forgeries (SSRF) using Ada's infrastructure.
While the CVSSv3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N - 5.3) indicates a Medium severity issue, we’ve elected to label this a Low severity issue due to the limited control an attacker has over the forged requests.
Ada uses Sentry.io for application monitoring, metrics, and error tracking within their environment. The tool was configured with automatic data scraping enabled when supplying certain error tracking endpoints with a "filename" in "stacktrace" fields. For example, by utilizing Ada's Sentry key, researchers were able to submit requests to Sentry's "store" endpoint with a "filename" belonging to a user-controlled endpoint. Researchers were then able to verify that Sentry made a request to our endpoint on Ada's behalf. The following screenshots demonstrate this.
The following public disclosures from other entities provide further details on this attack and how the feature may be disabled within Sentry:
- https://hackerone.com/reports/374737
- https://hackerone.com/reports/1467044
- https://shahjerry33.medium.com/blind-ssrf-sentry-misconfiguration-a68edc789db2
Solution
Ada.cx has remediated this issue. As this is a cloud-based service, no action is necessary for end users.
Disclosure Timeline
All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.
Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.
For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.
If you have questions or corrections about this advisory, please email [email protected]