CVE-2020-36620: A vulnerability was found in Brondahl EnumStringValues up to 4.0.0

Q: How do I fix CVE-2020-36620?

enumstringvalues: upgrade to 4.0.1. Exact commands for each OS are on this page.

Q: Is CVE-2020-36620 being exploited?

CVE-2020-36620 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-36620 affect?

CVE-2020-36620 affects enumstringvalues. Severity is low (CVSS 3.5). A vulnerability was found in Brondahl EnumStringValues up to 4.0.0. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferences_Uncache of the file EnumStringValues/EnumExtensions.cs. The mani

Q: How urgent is CVE-2020-36620?

Priority 30/100. No elevated risk signals yet.

Routine

LOW 3.5UPGRADE

CVE-2020-36620 is a low-severity flaw (CVSS 3.5) affecting enumstringvalues. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in Brondahl EnumStringValues up to 4.0.0. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferences_Uncache of the file EnumStringValues/EnumExtensions.cs. The manipulation leads to resource consumption. Upgrading to version 4.0.1 is able to address this issue. The name of the patch is c0fc7806beb24883cc2f9543ebc50c0820297307. It is recommended to upgrade the affected com

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.5 (Low)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.4% (top 28%)
CISA exploited list	No
Weakness	CWE-400
Published	2022-12-21
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: enumstringvalues project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-21 19:15 UTCPublished CVE record published
2026-06-17 03:15 UTCUpdated Record last modified

enumstringvalues project enumstringvalues UPGRADE

Affected: < 4.0.1

Fixed in: 4.0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy enumstringvalues || rpm -q enumstringvalues || enumstringvalues --version

2. UPGRADE to 4.0.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade enumstringvalues

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade enumstringvalues

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-36620?

enumstringvalues: upgrade to 4.0.1. Exact commands for each OS are on this page.

Is CVE-2020-36620 being exploited?

CVE-2020-36620 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-36620 affect?

CVE-2020-36620 affects enumstringvalues. Severity is low (CVSS 3.5). A vulnerability was found in Brondahl EnumStringValues up to 4.0.0. It has been declared as problematic. This vulnerability affects the function GetStringValuesWithPreferences_Uncache of the file EnumStringValues/EnumExtensions.cs. The mani

How urgent is CVE-2020-36620?

Priority 30/100. No elevated risk signals yet.

References

← Back to latest CVEs