<?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 22:02:33 +0000</lastBuildDate>
    <item>
      <title>GHSA-cx7h-h87r-jpgr — The kstring integration in gix-attributes is unsound</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cx7h-h87r-jpgr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: gix-attributes&lt;/p&gt;
&lt;p&gt;`gix-attributes` (in [`state::ValueRef`](https://github.com/Byron/gitoxide/blob/gix-attributes-v0.22.2/gix-attributes/src/state.rs#L19-L27)) unsafely creates a `&amp;amp;str` from a `&amp;amp;[u8]` containing non-UTF8 data, with the justification that so long as nothing reads the `&amp;amp;str` and relies on it being UTF-8 in the `&amp;amp;str`, there is no UB:&lt;/p&gt;
&lt;p&gt;```rust
// SAFETY: our API makes accessing that value as `str` impossible, so illformed UTF8 is never exposed as such.
```&lt;/p&gt;
&lt;p&gt;The problem is that the non-UTF8 `str` **is** exposed to outside code: first to the `kstring` crate itself, which requires UTF-8 in its documentation and may have UB as a consequence of this, but also to `serde`, where it propagates to e.g. `serde_json`, `serde_yaml`, etc., where the same problems occur.&lt;/p&gt;
&lt;p&gt;This is not sound, and it could cause further UB down the line in these places that can view the `&amp;amp;str`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: gix-attributes&lt;/p&gt;
&lt;p&gt;`gix-attributes` (in [`state::ValueRef`](https://github.com/Byron/gitoxide/blob/gix-attributes-v0.22.2/gix-attributes/src/state.rs#L19-L27)) unsafely creates a `&amp;amp;str` from a `&amp;amp;[u8]` containing non-UTF8 data, with the justification that so long as nothing reads the `&amp;amp;str` and relies on it being UTF-8 in the `&amp;amp;str`, there is no UB:&lt;/p&gt;
&lt;p&gt;```rust
// SAFETY: our API makes accessing that value as `str` impossible, so illformed UTF8 is never exposed as such.
```&lt;/p&gt;
&lt;p&gt;The problem is that the non-UTF8 `str` **is** exposed to outside code: first to the `kstring` crate itself, which requires UTF-8 in its documentation and may have UB as a consequence of this, but also to `serde`, where it propagates to e.g. `serde_json`, `serde_yaml`, etc., where the same problems occur.&lt;/p&gt;
&lt;p&gt;This is not sound, and it could cause further UB down the line in these places that can view the `&amp;amp;str`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cx7h-h87r-jpgr</guid>
    </item>
  </channel>
</rss>
