CVE-2020-20136

QuantConnect Lean versions from 2.3.0.0 to 2.4.0.1 are affected by an insecure deserialization vulnerability due to insecure configuration of TypeNameHandling…

published December 14, 2020

CVSS
—
EPSS
2%
Percentile
74.7
In the wild
Unconfirmed
What it is

⚠️ A tiny misconfiguration creates a gaping hole! The insecure deserialization flaw in QuantConnect Lean could let attackers inject harmful data just by sending a crafted JSON file. 🔥 Think of it like a restaurant that allows customers to customize their orders without checking the ingredients — if someone slips in a dangerous item, the whole meal gets compromised! An attacker can manipulate the deserialization process to execute malicious code, potentially taking control of your system. This could lead to unauthorized data access or unexpected behavior in your application, which is absolutely devastating!

Put simply

Think of it like a restaurant that allows customers to customize their orders without checking the ingredients — if someone slips in a dangerous item, the whole meal gets compromised! This vulnerability arises from the insecure configuration of the TypeNameHandling property in the Json.NET library, which can allow dangerous types to be instantiated based on untrusted input.

What to do

An attacker can manipulate the deserialization process to execute malicious code, potentially taking control of your system. This could lead to unauthorized data access or unexpected behavior in your application, which is absolutely devastating! To protect yourself, upgrade QuantConnect Lean to version 2.4.0.2 or later as soon as possible. Additionally, review your configuration settings to ensure TypeNameHandling is set securely, preventing harmful types from being executed. 🛡️ You've got this! Follow these steps, and you'll have your system secured in no time! 🚀

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.01537 · 74.7th percentile
Published
2020-12-14T18:30Z
EPSS history
Timeline
  • 14 DEC 18:30Z
    QuantConnect Lean versions from 2.3.0.0 to 2.4.0.1 are affected by an insecure deserialization vulnerability due to insecure configuration of TypeNameHandling…
    cvelistv5