<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 09 Oct 2026 23:11:17 +0000</lastBuildDate>
    <item>
      <title>cnvd-2022-62201</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2022-62201</link>
      <description>cnvd-2022-62201</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2022-62201</guid>
    </item>
    <item>
      <title>EUVD-2026-233950</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233950</link>
      <description>EUVD-2026-233950</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233950</guid>
    </item>
    <item>
      <title>fkie_cve-2022-31100</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-31100</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-31100</guid>
    </item>
    <item>
      <title>GHSA-8v9w-p43c-r885 — Reachable Assertion in rulex</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8v9w-p43c-r885</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: rulex&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches
The crashes are fixed in version **0.4.3**. Affected users are advised to update to this version.&lt;/p&gt;
&lt;p&gt;### Workarounds
You can use `catch_unwind` to recover from panics.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in [rulex](https://github.com/rulex-rs/rulex/issues)
* Email me at [ludwig.stecher@gmx.de](mailto:ludwig.stecher@gmx.de)&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;Credit for finding these bugs goes to&lt;/p&gt;
&lt;p&gt;- [cargo fuzz](https://github.com/rust-fuzz/cargo-fuzz) and [afl.rs](https://github.com/rust-fuzz/afl.rs)
- [evanrichter](https://github.com/evanrichter)
- [ForAllSecure Mayhem](https://forallsecure.com/)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: rulex&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Patches
The crashes are fixed in version **0.4.3**. Affected users are advised to update to this version.&lt;/p&gt;
&lt;p&gt;### Workarounds
You can use `catch_unwind` to recover from panics.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in [rulex](https://github.com/rulex-rs/rulex/issues)
* Email me at [ludwig.stecher@gmx.de](mailto:ludwig.stecher@gmx.de)&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;Credit for finding these bugs goes to&lt;/p&gt;
&lt;p&gt;- [cargo fuzz](https://github.com/rust-fuzz/cargo-fuzz) and [afl.rs](https://github.com/rust-fuzz/afl.rs)
- [evanrichter](https://github.com/evanrichter)
- [ForAllSecure Mayhem](https://forallsecure.com/)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8v9w-p43c-r885</guid>
    </item>
    <item>
      <title>gsd-2022-31100</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-31100</link>
      <description>gsd-2022-31100</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-31100</guid>
    </item>
    <item>
      <title>RUSTSEC-2022-0031 — Panic due to improper UTF-8 indexing</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2022-0031</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: rulex&lt;/p&gt;
&lt;p&gt;When parsing untrusted rulex expressions, rulex may panic, 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.&lt;/p&gt;
&lt;p&gt;The flaw was corrected in commits `fac6d58b25` and `330b3534e7` by using
`len_utf8()` to derive character width in bytes instead of assuming ASCII
encoding of 1 byte per char.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: rulex&lt;/p&gt;
&lt;p&gt;When parsing untrusted rulex expressions, rulex may panic, 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.&lt;/p&gt;
&lt;p&gt;The flaw was corrected in commits `fac6d58b25` and `330b3534e7` by using
`len_utf8()` to derive character width in bytes instead of assuming ASCII
encoding of 1 byte per char.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2022-0031</guid>
    </item>
  </channel>
</rss>
