Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact When parsing untrusted rulex expressions, the stack may overflow, possibly enabling a Denial of Service attack. This happens when parsing an expression with several hundred levels of nesting, causing the process to abort immediately. 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 process running rulex aborts due to a stack overflow. Patches The crash is fixed in version 0.4.3. Affected users are advised to update to this version. Workarounds None. For more information If you have any questions or comments about this advisory: Open an issue in rulex Email me at ludwig.stecher@gmx.de Credits Credit for finding these bugs goes to - evanrichter - ForAllSecure Mayhem - cargo fuzz and afl.rs
Recommended action: Upgrade to 0.4.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact 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. Patches The crashes are fixed in version 0.4.3. Affected users are advised to update to this version. Workarounds You can use catchunwind to recover from panics. For more information If you have any questions or comments about this advisory: Open an issue in rulex Email me at ludwig.stecher@gmx.de Credits Credit for finding these bugs goes to - cargo fuzz and afl.rs - evanrichter - ForAllSecure Mayhem
Recommended action: Upgrade to 0.4.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.