You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have identified a potential security vulnerability in the code where external data sources are being deserialized using Newtonsoft.Json with TypeNameHandling.All enabled. This setting allows the deserialization of types based on the type information present in the JSON payload. While convenient for polymorphic deserialization, it can also pose a security risk if the JSON data comes from untrusted sources. This setting could potentially be exploited for remote code execution (RCE) attacks if not handled carefully.
The text was updated successfully, but these errors were encountered:
contione
changed the title
Security concern regarding the usage of TypeNameHandling.All in JsonSerializerSettings
Security Risk in TypeNameHandling.All in JsonSerializerSettings
Jul 23, 2024
contione
changed the title
Security Risk in TypeNameHandling.All in JsonSerializerSettings
[Question]:Security Risk in TypeNameHandling.All in JsonSerializerSettings
Aug 13, 2024
Issue Description:
I have identified a potential security vulnerability in the code where external data sources are being deserialized using Newtonsoft.Json with TypeNameHandling.All enabled. This setting allows the deserialization of types based on the type information present in the JSON payload. While convenient for polymorphic deserialization, it can also pose a security risk if the JSON data comes from untrusted sources. This setting could potentially be exploited for remote code execution (RCE) attacks if not handled carefully.
Code Reference:
workflow-core/src/providers/WorkflowCore.Providers.Azure/Models/PersistedWorkflow.cs
Line 31 in a761d78
The text was updated successfully, but these errors were encountered: