strikeentco set up to 1.0.1 type confusion

Summaryinfo

A vulnerability was found in strikeentco set up to 1.0.1. It has been rated as problematic. The affected element is an unknown function. Performing a manipulation results in type confusion. This vulnerability is reported as CVE-2021-23497. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, was found in strikeentco set up to 1.0.1. This affects an unknown function. The manipulation with an unknown input leads to a type confusion vulnerability. CWE is classifying the issue as CWE-843. The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. This is going to have an impact on availability.

The weakness was disclosed 02/04/2022. The advisory is shared at snyk.io. This vulnerability is uniquely identified as CVE-2021-23497 since 01/08/2021. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.0.2 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• strikeentco

Name

• set

Version

• 1.0.0
• 1.0.1

License

• open-source

Website

• Product: https://github.com/strikeentco/set/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion