A security update for New Relic's .NET agent fixes a vulnerability that made it possible for the agent to send sensitive information to New Relic during an error trace by capturing query parameters from the referer header.
Release date: January 12, 2017
Vulnerability identifier: NR17-02
The following New Relic agent versions are affected:
|Name||Affected version||Notes||Remediated version|
|.NET agent||5.11 - 5.23||Only when Async is enabled||6.6|
|.NET agent||6.0 - 6.5||6.6|
New Relic's .NET agent collects the request headers during an error trace to help determine the root cause of problems. The referer header is the URI that identifies the address of the webpage that linked to the resource being requested. It is possible that the referer URI may contain sensitive information in the request query parameters. New Relic has found that the query parameters are not properly stripped during the error trace. This update fixes this by stripping the query parameters from the referer in the request header before sending this data to New Relic.
- Async is disabled by default in .NET agent versions 5.11.0 - 5.23.0.
- Best practices recommend not using query parameters to pass sensitive data.
New Relic has not identified any workarounds for this vulnerability.
Report security vulnerabilities to New Relic
New Relic is committed to the security of our customers and their data. If you believe you have found a security vulnerability in one of our products or websites, we welcome and greatly appreciate you reporting it to New Relic's coordinated disclosure program. For more information, see Reporting security vulnerabilities.
For more help
Additional documentation resources include: