13 matches found
EUVD-2022-7749
Malicious code in bioql PyPI...
CVE-2020-36620
A vulnerability was found in Brondahl EnumStringValues up to 4.0.0. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferencesUncache of the file EnumStringValues/EnumExtensions.cs. The manipulation leads to resource consumption. Upgrading to versi...
Denial Of Service (DoS)
enumstringvalues is vulnerable to denial of service DoS attacks. A malicious user is able to cause excessive resource consumption via the function GetStringValuesWithPreferencesUncache of the file EnumStringValues/EnumExtensions.cs, resulting in an application crash...
GHSA-VQ23-HWG7-HXRH EnumStringValues vulnerable to Uncontrolled Resource Consumption
A vulnerability was found in Brondahl EnumStringValues 4.0.1. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferencesUncache of the file EnumStringValues/EnumExtensions.cs. The manipulation leads to resource consumption. Upgrading to version 4.0...
EnumStringValues vulnerable to Uncontrolled Resource Consumption
A vulnerability was found in Brondahl EnumStringValues 4.0.1. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferencesUncache of the file EnumStringValues/EnumExtensions.cs. The manipulation leads to resource consumption. Upgrading to version 4.0...
CVE-2020-36620
A vulnerability was found in Brondahl EnumStringValues up to 4.0.0. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferencesUncache of the file EnumStringValues/EnumExtensions.cs. The manipulation leads to resource consumption. Upgrading to versi...
CVE-2020-36620
A vulnerability was found in Brondahl EnumStringValues up to 4.0.0. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferencesUncache of the file EnumStringValues/EnumExtensions.cs. The manipulation leads to resource consumption. Upgrading to versi...
Design/Logic Flaw
A vulnerability was found in Brondahl EnumStringValues up to 4.0.0. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferencesUncache of the file EnumStringValues/EnumExtensions.cs. The manipulation leads to resource consumption. Upgrading to versi...
CVE-2020-36620 Brondahl EnumStringValues EnumExtensions.cs GetStringValuesWithPreferences_Uncache resource consumption
A vulnerability was found in Brondahl EnumStringValues up to 4.0.0. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferencesUncache of the file EnumStringValues/EnumExtensions.cs. The manipulation leads to resource consumption. Upgrading to versi...
CVE-2020-36620 Brondahl EnumStringValues EnumExtensions.cs GetStringValuesWithPreferences_Uncache resource consumption
A vulnerability was found in Brondahl EnumStringValues up to 4.0.0. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferencesUncache of the file EnumStringValues/EnumExtensions.cs. The manipulation leads to resource consumption. Upgrading to versi...
EnumStringValues 资源管理错误漏洞
EnumStringValues is a library for mapping between strings and enumerations from the individual developer Michael McLean. A resource management error vulnerability exists in EnumStringValues version 4.0.17, which originates in the function GetStringValuesWithPreferencesUncache in the file...
PT-2022-7099 · Brondahl · Brondahl Enumstringvalues
Name of the Vulnerable Software and Affected Versions: Brondahl EnumStringValues versions up to 4.0.0 Brondahl EnumStringValues version 4.0.1 Description: The issue is related to the function GetStringValuesWithPreferences Uncache of the file EnumStringValues/EnumExtensions.cs in the Brondahl...
CVE-2020-36620
Summary: This CVE affects Brondahl EnumStringValues up to 4.0.0. The vulnerability is in GetStringValuesWithPreferences_Uncache (EnumExtensions.cs) and causes resource consumption. Documents consistently cite upgrading to 4.0.1 to address the issue, with the patch identified as c0fc7806beb24883cc...