rulex up to 0.4.2 Expression Parser assertion

Summaryinfo

A vulnerability, which was classified as critical, was found in rulex up to 0.4.2. This vulnerability affects unknown code of the component Expression Parser. Executing a manipulation can lead to assertion. This vulnerability is handled as CVE-2022-31100. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in rulex up to 0.4.2. It has been declared as critical. This vulnerability affects some unknown functionality of the component Expression Parser. The manipulation with an unknown input leads to a assertion vulnerability. The CWE definition for the vulnerability is CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. As an impact it is known to affect availability. CVE summarizes:

rulex is a new, portable, regular expression language. When parsing untrusted rulex expressions, rulex may crash, possibly enabling a Denial of Service attack. This happens when the expression contains a multi-byte UTF-8 code point in a string literal or after a backslash, because rulex tries to slice into the code point and panics as a result. This is a security concern for you, if your service parses untrusted rulex expressions (expressions provided by an untrusted user), and your service becomes unavailable when the thread running rulex panics. The crashes are fixed in version **0.4.3**. Affected users are advised to update to this version. The only known workaround for this issue is to assume that regular expression parsing will panic and to add logic to catch panics.

The weakness was released 06/28/2022 as GHSA-8v9w-p43c-r885. The advisory is shared for download at github.com. This vulnerability was named CVE-2022-31100 since 05/18/2022. There are neither technical details nor an exploit publicly available.

Upgrading to version 0.4.3 eliminates this vulnerability. Applying the patch fac6d58b25c6f9f8c0a6cdc4dec75b37b219f1d6 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.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• rulex

Version

• 0.4.0
• 0.4.1
• 0.4.2

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion