github.com/aws/amazon-ssm-agent-v0.0.0-20181107231829-b9654b268afc: 2 vulnerabilities (highest severity is: 9.8) - autoclosed #110
Labels
Mend: dependency security vulnerability
Security vulnerability detected by WhiteSource
Vulnerable Library - github.com/aws/amazon-ssm-agent-v0.0.0-20181107231829-b9654b268afc
An agent to enable remote management of your EC2 instances, on-premises servers, or virtual machines (VMs).
Library home page: https://proxy.golang.org/github.com/aws/amazon-ssm-agent/@v/v0.0.0-20181107231829-b9654b268afc.zip
Vulnerabilities
Details
CVE-2018-1285
Vulnerable Library - github.com/aws/amazon-ssm-agent-v0.0.0-20181107231829-b9654b268afc
An agent to enable remote management of your EC2 instances, on-premises servers, or virtual machines (VMs).
Library home page: https://proxy.golang.org/github.com/aws/amazon-ssm-agent/@v/v0.0.0-20181107231829-b9654b268afc.zip
Dependency Hierarchy:
Found in base branch: brightcove
Vulnerability Details
Apache log4net versions before 2.0.10 do not disable XML external entities when parsing log4net configuration files. This allows for XXE-based attacks in applications that accept attacker-controlled log4net configuration files.
Publish Date: 2020-05-11
URL: CVE-2018-1285
CVSS 3 Score Details (9.8)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Release Date: 2020-05-11
Fix Resolution: log4net - 2.0.10
WS-2022-0161
Vulnerable Library - github.com/aws/amazon-ssm-agent-v0.0.0-20181107231829-b9654b268afc
An agent to enable remote management of your EC2 instances, on-premises servers, or virtual machines (VMs).
Library home page: https://proxy.golang.org/github.com/aws/amazon-ssm-agent/@v/v0.0.0-20181107231829-b9654b268afc.zip
Dependency Hierarchy:
Found in base branch: brightcove
Vulnerability Details
Newtonsoft.Json prior to version 13.0.1 is vulnerable to Insecure Defaults due to improper handling of expressions with high nesting level that lead to StackOverFlow exception or high CPU and RAM usage. Exploiting this vulnerability results in Denial Of Service (DoS). \n\nThe serialization and deserialization path have different properties regarding the issue.\n\nDeserializing methods (like
JsonConvert.DeserializeObject
) will process the input that results in burning the CPU, allocating memory, and consuming a thread of execution. Quite high nesting level (>10kk, or 9.5MB of{a:{a:{...
input) is needed to achieve the latency over 10 seconds, depending on the hardware.\n\nSerializing methods (likeJsonConvert.Serialize
orJObject.ToString
) will throw StackOverFlow exception with the nesting level of around 20k.\n\nTo mitigate the issue one either need to update Newtonsoft.Json to 13.0.1 or setMaxDepth
parameter in theJsonSerializerSettings
. This can be done globally with the following statement. After that the parsing of the nested input will fail fast withNewtonsoft.Json.JsonReaderException
:\n\n\nJsonConvert.DefaultSettings = () => new JsonSerializerSettings { MaxDepth = 128 };\n
\n\nRepro code:\n\n//Create a string representation of an highly nested object (JSON serialized)\nint nRep = 25000;\nstring json = string.Concat(Enumerable.Repeat(\"{a:\", nRep)) + \"1\" +\n string.Concat(Enumerable.Repeat(\"}\", nRep));\n\n//Parse this object (leads to high CPU/RAM consumption)\nvar parsedJson = JsonConvert.DeserializeObject(json);\n\n// Methods below all throw stack overflow with nRep around 20k and higher\n// string a = parsedJson.ToString();\n// string b = JsonConvert.SerializeObject(parsedJson);\n
\n\n### Additional affected product and version information\nThe original statement about the problem only affecting IIS applications is misleading. Any application is affected, however the IIS has a behavior that stops restarting the instance after some time resulting in a harder-to-fix DoS.**Publish Date: 2022-06-22
URL: WS-2022-0161
CVSS 3 Score Details (7.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Release Date: 2022-06-22
Fix Resolution: Newtonsoft.Json - 13.0.1;Microsoft.Extensions.ApiDescription.Server - 6.0.0
The text was updated successfully, but these errors were encountered: