.NET Core agent release notes

Updated Protect AgentLib to address SQLi false positives on escaped SQL values. (DOTNET-5406)

Expanded the logging and null reference handling in the bootstrapper for the agent installer. (DOTNET-5397)

Made more performance improvements for thread static signatures. (DOTNET-3883, DOTNET-5380)

The agent installer now handles .NET Framework 4.6.2 requirement when installed but not cached. (DOTNET-5396)

The Agent Explorer now properly shows moved or deleted IIS Express applications. (DOTNET-5390)

Added support for .NET 8.0

Made performance improvements for interned strings. (DOTNET-3597)

Made performance improvements for thread static methods. (DOTNET-3848, DOTNET-3849)

Added a warning to the .NET Core installer when unchecking Restart IIS when required. (DOTNET-5306)

Added Microsoft signatures for Assess Path Traversal. (DOTNET-5314)

Cleaned up log messages when the profiler fails to attach to an application. (DOTNET-5335)

Reduced memory usage when logging messages. (DOTNET-5336)

Added missing String.Join method signature. (DOTNET-5378)

Improved performance when instrumenting LDAP APIs. (DOTNET-3844)

Improved performance instrumenting EscapeForJs. (DOTNET-3845)

Improved performance when instrumenting enum parsing. (DOTNET-3846)

Improved performance when instrumenting string parsing for built-in types. (DOTNET-3847)

improved performance when instrumenting XmlReader. (DOTNET-3867)

The agent now prevents potentially sending user data to Sentry if an exception is thrown when doing MVC route discovery. (DOTNET-5299)

Improved performance when tracing data through AnchorTagHelpers. (DOTNET-5302)

Fixed an issue with the security log not being created if Protect is turned on in the Contrast web interface. (DOTNET-5241)

The security log no longer contains an empty source. (DOTNET-5256)

The agent prevents false positives in certain cases when a pooled array is reused. (DOTNET-5234)

Body capture is now disabled when the agent detects a gRPC request. (DOTNET-5000)

Performance timings in the log files now include request start and request end. (DOTNET-5254)

AgentLib logging environment variables are now set with the agent's native IIS module. (DOTNET-5068)

Fixed a bug that caused errors when sending effective configuration information to Contrast. (DOTNET-5242)

The telemetry service is no longer reported as a web service component. (DOTNET-5232)

Improved deduping by updating URI normalization to new standard. (DOTNET-5128)

Contrast now applies code and URL exclusions to the Protect path-traversal-semantic-file-security-bypass rule. (DOTNET-5167)

The agent now tracks propagation through more System.Text.Json methods. (DOTNET-3874)

The agent now tracks propagation through implicit conversion of string to ReadOnlySpan<T> (DOTNET-5011)

Added missing StringBuilder method signatures (DOTNET-5015)

Diagnostics now check CORECLR_PROFILER_PATH when running the check-process command (DOTNET-5075)

The agent now sends effective configuration data to Contrast. (DOTNET-5127)

The agent now attaches properly under ARM64 Alpine.

The Agent now supports applications on Ubuntu running ARM64 architecture.

Enhanced the performance when processing Span<T> objects.

Improved the performance when processing thread static methods.

The agent now sends the protocol when sending URIs for web services. (DOTNET-5145)

The agent no longer attaches to the Contrast.AgentExplorer.Backend.exe process. (DOTNET-5116)

Improved performance when tracing Span propagation. (DOTNET-3853, DOTNET-3856, DOTNET-3860, DOTNET-3861, DOTNET-3870, DOTNET-5034, DOTNET-5036, DOTNET-5037, DOTNET-5038, DOTNET-5040)

Changed the profiler to have Azure Functions Service Bus support turned on by default. (.NET-5080)

Fixed an issue with a path traversal false positive that the agent reported when input contained only '/' and/or '.' characters. (.NET-5051)

Resolved an issue that caused the agent to report a false positive for SQL injection in Protect. (.NET-5066)

The checks on the app_pool_allowlist/denylist are now done earlier during runtime in order to be more efficient. (DOTNET-5020)

Removed System.Data.DataSet from the list of gadgets that could trigger an untrusted deserialization vulnerability.(DOTNET-5045)

The agent's log files no longer trigger a path traversal vulnerability. (DOTNET-5054)

Route discovery continues to work when a bad JSON exists on an Azure Function app's host.json file. If this issue occurs, the routes will have no prefix. (DOTNET-5058)

Fixed an exception that occurred during log clean up when one application is running as administrator and another is running as a normal user. (DOTNET-4963)

The agent no longer reports false positive unvalidated-redirect in certain cases where the scheme/host were actually safe. (DOTNET-5008)

Thread safety issues with collections that could result in exceptions and performance degradation were addressed. (DOTNET-4986)

Added support for Telerik JavaScript encoding method signatures for XSS, so methods that use them should no longer result in xss vulnerabilities. (DOTNET-5002)

Added config flag agent.dotnet.debug.background_job_deny_list to disable background jobs

Improved the handling of AgentLib exceptions

Installers now remove all registry keys when uninstalled

Agent Explorer finds a different port if its default port is already in use

Agent Explorer uses platform-specific paths for the Native Module for applications under IIS Express

Fixed an issue that caused the Agent Explorer to crash on startup

Agent disables itself with a 404 message only if the response body includes an invalid application message

Fixed localization text in the installer

Log clean up is now done by one instance of the agent, thereby reducing resource consumption on start up

The agent has better logging if it cannot get the per-user config in certain cases

Agent Explorer displays a better message for applications that are not instrumented due to an application allowlist or denylist

Installer no longer hangs if IIS is not installed and it tries to run AppCmd

Agent no longer reports crypto-weak-randomness when certain database clients are used

Service Bus queues can be excluded in an Azure Functions application using a Service Bus trigger.

Improved documentation on expectations for setting Azure Functions environment variables.

The agent now uses the agent-lib library by default.

Improved the documentation for the diagnostics 'memory-usage' verb.

Offset starting background jobs in the agent to reduce startup resource usage.

Service Bus gRPC endpoints are no longer found during Azure Functions route discovery.

Profiler no longer attaches to Contrast.AgentExplorer.exe.

Improved performance for log cleanup.

Agent now supports chaining with Aternity.

Agent now reports Redis database connections to FlowMap for connections using the StackExchange Redis driver.

Azure Function apps are named after the assembly rather than the host.

The installer bootstrapper does not block bundle downgrades on silent installations.

Assess and Protect now detect SQL-injection vulnerabilities for PostgresSQL databases that use the npgsql library.

Agent now reports PostgresSQL database connections to FlowMap for connections using the npgsql library.

Expanded the ValueStringBuilder support for some propagation signatures.

Expanded Assess coverage of String.Normalize APIs.

Attacks that Protect detects now include the parameter names for attacks originating from model-bound values set from parameters sources.

Improved agent reporting of View components for FlowMaps in the Contrast web interface.

This release includes a new version of Agent Explorer with several bug fixes and UI improvements.

The agent now reports web service components that the application uses to populate the Contrast Flow Map.

The agent now supports attaching a debugger to .NET 6 applications without requiring the DOTNET_EXTERNAL_DebuggerLaunchDisablesCodeVersioning=0 environment variable.

The invariant culture is now used when writing Protect events to syslog. (DOTNET-4661)

When both the agent package and the installed agent were deployed to the same server, the agent package's instrumentation would load the installed agent's sensors component. This issue is now fixed. (DOTNET-4683)

Assess would report an XSS when ASPNET Core MVC used the URL, encoded by the framework when necessary, in generated form actions. This has been fixed. (DOTNET-4623)

The agent will now more reliably detect and report databases to Flow Map. (DOTNET-2199)

Added support for .NET 7.

Agent Explorer now shows statistics for the number of vulnerabilities, number of attacks, and external services that agents observe, as well as information for libraries seen and number of classes that each library uses.

Assess could sometimes report vulnerabilities involving data flow using interned strings. This issue is now fixed. (DOTNET-4589)

Further reduced the number of allocations that Contrast Assess uses to track dataflow through StringBuilder.Replace APIs.

Significantly improved performance, particularly for allocations that Assess uses to track dataflow through StringBuilder.Replace APIs.

In Agent Explorer, the detailed view of an agent now displays why a degraded or faulted agent is in a bad state.

In Agent Explorer, the Summary tab now shows a consistent number of agents across different components. (DOTNET-4580)

Agents running within .NET Core 3.1 applications failed to report to Agent Explorer. This issue is now fixed. (DOTNET-4579)

Applications could crash when running with Dynatrace OneAgent when an environment variable was changed to a null value. This issue is now fixed. (DOTNET-4594)

This issue was incorrectly reported as fixed in .NET Core 2.3.1.

Applications could crash when running with Dynatrace OneAgent when an environment variable was changed to a null value. This issue is now fixed. (DOTNET-4594)

Assess would incorrectly report a vulnerability when the value of the content-length header was used in a sink such as a database query. This issue is now fixed. (DOTNET-4537)

The .NET Core agent for IIS installer now includes Agent Explorer, a separate GUI application that provides high-level information about locally running .NET and .NET Framework agents. Use Agent Explorer to see high-level information such as:

Protect now reports the IP address of an attack in more scenarios.

The .NET Core for IIS agent now supports running alongside Dynatrace in both in-process and out-of-process modes. Previously the agent only supported running alongside Dynatrace when using in-process hosting. (DOTNET-4572)

.NET 7 RC1 is now supported.

Input exclusions now have full regular expression support.

Fixed a reported issue where the diagnostics executable would crash with an error Contrast.AgentLib was not found.

The agent would observe admin routes within Azure Functions that are only executed by the Azure Functions internals. The agent no longer reports these admin routes (DOTNET-4464).

Agent upgrades for the installed IIS agent would fail when an agent was installed with a custom data directory. This issue has been fixed. (DOTNET-4453)

The Agent Upgrade Service would only check for updates after restarting a second time, this has now been fixed. (DOTNET-4318)

Agent will now report SMTP Injection vulnerabilities under Assess.

On Windows Server 2012, the IIS installer will now warn users to install VC++ redistributable package necessary for the agent's upgrade service.

The agent would fail to clean up rolled over log files from native components. This has been fixed. (DOTNET-4314)

Assess hsts-header-missing previously checked the presence and value of the strict-transport-security header for requests made over TLS only. The rule will now also check for the strict-transport-security header if the X-Forwarded-Proto header indicates the request was made over TLS but TLS was terminated before reaching the application.

Diagnostics now offers a read-config option that will report on the effective configuration of currently running instrumented applications on the server.

Improved the accuracy of Protect XXE detection, fixing a false negative.

Assess previously reported the usage of a weak hash algorithm within Microsoft's Application Insight's snapshot collector. This will no longer be reported. (DOTNET-4252)

Agent could cause an application error when capturing the application's response when the HTTP context was null at the end of the request. This has been fixed. (DOTNET-4219)

Resolved a performance regression only present in version 2.1.15.

Improved Assess response capture, especially with regards to reducing the agent's impact to response streaming.

Improved detection of when the agent is running in an Azure Functions environment.

The agent did not send assess.tags with the "preflight" vulnerability check (but did send this information with the vulnerability report.) The agent now sends the expected information with both messages. (DOTNET-4157)

Assess analysis did not include ASPNET Core MVC model-bound path parameters. The agent will now correctly find vulnerabilities originating from a model-bound path parameter. (DOTNET-4163)

Added Assess sanitizers for mganss' HtmlSanitizer APIs. (DOTNET-4033)

Reduced the amount of memory used by the runtime for all libraries not instrumented by the agent. This has resulted in 5-10% reduction in process memory.

Improved Assess taint tracking for validation methods.

Assess will no longer propagate on HttpRequest.PathBase .(DOTNET-4117)

Improved accuracy of Assess URL character tracking to exclude the port number. (DOTNET-4093)

Assess will no longer report path traversal on Linux systems when ASP.NET Core reads time zone info from the file system. (DOTNET-4062)

Minor performance improvements to the cost of calling into Contrast sensors from instrumented code.

Added diagnostics check-access option to test that a Windows user has access to agent profiler and sensor components.

Improved cookie value parsing logic to avoid reporting that an invalid cookie is missing HttpOnly or secure flags.

Protect untrusted deserialization did not respect URL exclusions. (DOTNET-4019)

Agent failed to detect web service flow map components when an application used .NET Core's dependency injection (i.e., services.AddHttpClient).(DOTNET-4023)

Agent will now report web service components which can be viewed on the application's flow map diagram. (This item mistakenly appeared in release notes for 2.1.6)

Expanded APIs used to detect unvalidated redirect vulnerabilities under Assess.

Diagnostics validate-yaml will now validate application.metadata and application.session_metadata values follow expected format.

Added new deep-connect diagnostics command to help troubleshoot agent communication with Contrast.

Semantic Path Traversal attacks would be detected and blocked by the agent but failed to report to Contrast. (DOTNET-3978)

Diagnostics cert-info command's validation of certificates now more closely matches the agent's HttpClient's certificate validation.

The Azure App Service Site Extension's XDT in version 2.1.6 included a bad transform that caused the App Service instance to crash. This has been fixed. (DOTNET-3983)

Improved reporting of library class names to exclude compiler-generated types.

Added Protect support for GraphQL inputs.

Agent will now report web service components which can be viewed on the application's flow map diagram.

Diagnostics config-keys will now provide descriptions for special Contrast environment variables that can be used to configure specific agent behavior (e.g., CONTRAST_CONFIG_PATH to set the path of the agent's configuration file.)

Agent instrumentation of Utf8JsonReader lead to an application crash under 32-bit processes.

In some rare cases, the Azure App Service Site Extension could fail to cleanly upgrade because the agent's profiler component was locked. Agent components within the site extension are now housed in a version-specific directory. Note that users that have manually specified the path to agent components will need to update these paths. This should not be common as the Site Extension automatically sets the environment variables with the correct paths necessary to load the agent.

Improved performance of Assess analysis, especially with regards to methods with internal implementations that make heavy use of Span APIs.

Assess potential sanitizers and validators will now be automatically reported to Contrast by default.

.NET Core for IIS agent now enables profiler chaining by default.

Assess now supports GraphQL sources and route coverage for graphql-dotnet library versions 4.0.1+.

Improved performance by reducing cost of jumping from instrumented code to Contrast sensors.

Improved performance of Assess analysis of System.Text.Json API calls.

The agent's sensors component did not respect a custom data directory set during install. (DOTNET-3739)

Diagnostics' system-info command failed to gather information about IIS application pools and applications. (DOTNET-3670)

Improved performance of Assess and Protect analysis by reducing the cost of calling into Contrast code from instrumented code.

Improved performance of Assess analysis of application code with data flow within LINQ where clauses.

Fixed an issue where agent logs indicated an error due to a missing default configuration value. (DOTNET-3633)

Fixed an issue where the agent's Upgrade Service component could crash when instrumented by the Contrast .NET Core agent earlier than 2.1.0. Note that this would only occur if a user set global environment variables to add the Contrast .NET Core agent's profiler. (DOTNET-3689)

Routes included the application's virtual path when deployed to IIS.  (DOTNET-3632)

Now supports profiler chaining with AppDynamics.

Now supports Assess log-injection.

When an instrumented application used a static DI container with cookie options then the agent would cause the application to fail to start. (DOTNET-3630)

.NET Core 2.1.0 adds support for applications targeting .NET 6.

Improved Assess data flow analysis through APIs using Span, Memory, ValueTask, ValueStringBuilder, and StringSegment types.

Agent now recognizes specific DateOnly and TimeOnly APIs as validators for Assess.

Added route coverage support for .NET 6's minimal API structure.

The .NET Core agent now supports Assess Stored XSS and Trust Boundary Violation rules.

Minor performance improvements.

Improved security of the agent upgrade service.

NullReferenceException when agent attempted to determine the version of .NET Core from an unusual command line. (DOTNET-3454)

Assess SQL Injection false positive when numeric values were safely used by Entity Framework Core internally. (DOTNET-3435)

Improved Assess data flow coverage through String.Format and JsonEncodedText.Encode.

Added Assess and Protect handling for when System.Text.Json serialization is set as the formatter/model-binder for ASP.NET Core.

Further reduced the amount of memory used by the agent's profiler component.

Reduced agent's overhead on each request.

The installed .NET Core for IIS agent now includes an auto-upgrade service that, if enabled in the service's configuration, will automatically upgrade the agent to the latest version on NuGet.

Improved Assess coverage APIs involving Span<T>, Range, and Index parameters.

The agent will no longer report weak hash algorithm used by the Azure Storage client SDK.

The agent would fail to discover routes declared using ASPNET Core MVC 3+ endpoint-style routing. (DOTNET-3265)

Further reduced memory usage of the agent's profiler component.

Improved Assess coverage of Memory<T> and MemoryExtension APIs.

Added official support for RHEL 7 and 8.

The agent could fail to report discovered routes to Contrast. (DOTNET-3234)

Reduced the amount of memory used by the agent's profiler component.

Improved Assess coverage of Memory<T> and Span<T> APIs.

Agent did not respect URL-based exclusions for Assess response-based rules. (DOTNET-3161)

Protect will no longer report semantic SQL findings on queries constructed safely using EF Core 2.1/3.1/5.0.

Profiler will now log all profiler settings, not just settings from the YAML file.

Profiler will no longer instrument diagnostics/powershell/powershell core.

Improved Assess coverage of APIs that return task.

Protect will no longer report semantic SQL chaining on queries constructed safely using LINQ 2 SQL.

Protect will no longer report use of dangerous functions on queries constructed safely using Entity Framework.

Agent's interaction with ASPNET Core's DI container could cause applications built on top of a Boilerplate template to not start up. (DOTNET-3038)

Assess will no longer report untrusted deserialization against JsonNET JsonSerializerProxy. (DOTNET-3031)

Assess false positive when using JsonSerializerProxy with Json.NET deserialization. (DOTNET-3031)

Agent did not send sessionId when reporting routes. (DOTNET-3021)

Improved performance of calling into Contrast code from instrumented methods.

Improved agent startup performance.

Will now discover and observe health check routes.

Will now observe endpoint routing routes (discovery was implemented in a previous version).

Agent will now discover endpoint routing routes.

Improved memory usage of logging communication with Contrast.

Agent will now discover and observe routes used by routing middleware handlers.

Reduced memory used by agent to capture stack traces.

Improve performance of capturing repeated stack traces under Protect.

Improved Assess coverage of ref struct objects when using the Common Instrumentation Engine (CIE).

Improved Assess sql-injection coverage of EF Core APIs.

Expanded coverage of Protect cmd-injection rule.

Will now discover health check routes.

Diagnostics now offers create-script to create deployment "scripts" for the local machine. Currently supports PowerShell, bash, launch settings, and web.config.

Diagnostics check-process will now inspect logs in the logs directory specified by environment variable (if set).

Agent will now report agent errors to telemetry.

Agent could fail to identify Assess sources when inspecting a model bound object that mixed JObject type within a POCO type. (DOTNET-2534)

Library reporting could fail on obfuscated assemblies. (DOTNET-2846)

Improved logging when both CLR and CoreCLR are in the same process.

Improved instrumentation performance under CLR Instrumentation Engine (CIE).

Improved logging for unsupported .NET Core runtime versions.

Added verb + url reporting for .NET Core Razor Pages discovered routes.

Fixed an error in parsing certain SQL queries in Protect semantic SQL rules. (DOTNET-646)

Fixed a memory leak. (DOTNET-2771)

Agent initialization will now log the final resolved value for assess.enable and protect.enable.

Improved route discovery for controller actions using convention or pattern-based routing.

.NET Core agent hangs on async tasks. (SUP-2667)

Improved accuracy for async APIs under Assess.

Accurate reporting of the verb and URL parameters for unexercised routes when using the NetCore framework.

Added support for server.path configuration.

The agent will now report the host of Web Service components.

Improved agent performance by alleviating common agent hot spots.

Improved Assess data propagation on asynchronous methods.

Improved Assess detection of unsafe cryptographic algorithms.

Agent does not properly handle valid tls_versions configuration: tls|tls11|tls12 (DOTNET-2551)

The agent's profiler component chooses not to instrument a process when .NET Framework runtime was loaded first but the environment variable indicated .NET Core. (SUP-2225)

Improved application archiving capabilities. Once an application is archived in the Contrast web interface, the .NET Core agent will be disabled without needing an IIS restart.

Different signatures for the same dataflow reports duplicate routes. (SUP-2345)

All agent configuration settings referring to the terms blacklist and whitelist have been changed to denylist and allowlist, respectively. For example, agent.dotnet.app_pool_whitelist is now agent.dotnet.app_pool_allowlist. The agent will continue to respect the old configuration names until August 2nd, 2022.

Protect will now mask sensitive data in the attack vector if enabled in the Contrast web interface.

Refined crypto-bad-mac rule to ignore .NET Core library code.

Added support for additional .NET Core deployment types (self-contained and framework dependant executables).

Protect path traveral in monitoring mode will now report a path-traversal probe when an attack goes through a "path resolution API" such as Path.GetFullPath. (SUP-2190)

Self-contained .NET Core deployments are now supported.

Added checkpoints to ensure semantic SQL rules are not reported by the agent when the rule is disabled in the Contrast web interface.

Added support for framework dependent executables.

Removed agent.dotnet.enable_runtimeid_callbackhandler configuration.

Session based auto-verification policies didn’t change the vulnerability status. (SUP-2365)

The profiler will now log to syslog in the event of a major error or exception.

.NET Core agent has a problem on startup when an application specified a custom NLog configuration file. (SUP-2220)

The agent now supports .NET Core 5.

The agent now reports names of classes used as part of enhanced library usage.

The agent was reporting misleading route observation predictions upon route discovery. (DOTNET-2213)

The agent fails to start when Contrast provided a syslog configuration with messages at INFO level. (DOTNET-2310)

The agent caused an error during agent initialization if the console was disabled. (DOTNET-2283)

With this release, the CLR Instrumentation Engine (CIE) is fully supported. Custom CIE environment variables are no longer required and can be removed. (You may have to reinstall the site extension.)

Officially deprecated and removed CONTRAST__AGENT__DOTNET__CONTAINER. The configuration flag has no effect. All environments that required it, no longer require the flag to function.

Reduced the size of the Azure App Service Site Extension by removing diagnostics from the download. Diagnostics is still available for other deployment types.

Minor performance improvements under Protect's XSS.

When agent sensors failed to initialize under Windows, they would crash the IIS process with an "IOException: The handle is invalid." exception. (DOTNET-2253)

We will no longer support .NET Core 2.2 beginning with this version. This is keeping up with Microsoft’s support policy, and their announcement to end support for .NET Core 2.2 by Dec 23, 2019. If you are using .NET Core 2.2, please make sure to use the .NET Core agent version 1.5.20 or lower until you can upgrade your application’s .NET Core runtime.

The .NET Core agent now supports logging to stdout for managed code.

Found memory leak in correlation tasks. (SUP-2065)

Agent causes 500 if the app changes the maximum request body size. (SUP-2032, workaround available)

Telemetry now reports application framework and profiler chaining configurations.

Azure Service Fabric is supported as a deployment type for the .NET Core agent.

The agent does not respect the  api.certificate.ignore_cert_errors configuration property.

Telemetry is now enabled in the .NET Core agent in order to gather valuable data about the agent’s functionality. The data is all anonymous, no personal information is collected.

Agent fails to startup properly when application is archived. (SUP-1849)

Type scanning may throw an exception. (SUP-1671)

Improved logging around Virtual Patch usage.

Virtual patches for QueryString parameters do not work if the values contain structured data. (SUP-1763)

Improved logging around non-graceful shutdowns.

Added connect to contrast-dotnet-diagnostics to test the agent’s ability to connect to Contrast.

Added config-keys to contrast-dotnet-diagnostics to display configuration options supported by the agent.

Added cert-info to contrast-dotnet-diagnostics to display information about the certificate provided by the value of the api.url configuration setting.

Improved the performance of Protect SQL-Injection detection.

Improved the performance of Protect against XML-based inputs.

Added validate-yaml to contrast-dotnet-diagnostics to verify the agent’s contrast-security.yaml configuration file.

Improved the Assess analysis used to identify SSRF vulnerabilities to reduce the number of false positives reported by the agent.

Improved the Protect analysis used to analyze user inputs for potential SQL injection attacks to improve accuracy and performance.

The agent will now clean up old logs.

Removed the dependency on Microsoft.Extensions.Caching.Memory.

Improved performance of Protect XSS.

Improved performance of Protect SQL-Injection.

When the agent would report vulnerabilities for four response-based Assess rules related to CSP and HSTS, the report would be rejected by Contrast due to missing information. The agent now sends all expected information for these rules.

When an instrumented application defined a type using a large number of nested generic types, the agent could cause a StackOverflow error. This has now been fixed.

When a user would disable multiple Protect rules through the ‘contrast.protect.disabled_rules’ setting in the yaml file, the agent would not respect this setting. The agent will now respect this configuration setting.

When a user would disable logging, the agent’s profiler component would still log high level information during initialization. The profiler will no longer create a log when logging is disabled.

Improved detection of dangerous path use in Protect; specifically, when interacting with the file system (path-traversal-semantic-dangerous-paths rule) and in arguments to OS commands (cmd-injection-semantic-dangerous-paths rule).

The agent will no longer attempt to load under .NET Core versions less than 2.1 as these versions are not supported.

When an application sent a request to the same URL as the current request, the agent would report an SSRF vulnerability. This is fixed now.

When the agent would report an xcontenttype-header-missing vulnerability, Contrast would reject the vulnerability report due to missing information. The agent now sends all expected information for this vulnerability.

When an instrumented application closed the response stream, the agent could cause an application error. This is fixed now.

When an instrumented application seeked within a response stream, the agent could cause an application error. This is fixed now.

Added support for Linux Azure App Service.

Added support for Alpine.

Improved handling of scenarios where the agent would write repeated errors to log files, creating larger than necessary log files.

The agent will now log unknown configuration keys at startup. This should help with troubleshooting configuration issues (for example invalid yaml).

When applications redirected to a URL that had been validated using Url.IsLocalUrl, the agent would still report an unvalidated redirect vulnerability. The agent will now respect the Url.IsLocalUrl validator.

A race condition around requests for configuration values that did not have default values could lead to an unhandled error in the agent. The race condition has been fixed, default configuration values have been provided for all configuration options, and missing default configuration values are now properly handled.