<?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://vulnerability.circl.lu</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>Wed, 30 Sep 2026 03:09:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-24898 — rust openssl ssl::select_next_proto use after free</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-24898</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; sfackler rust-openssl&lt;/p&gt;
&lt;p&gt;rust-openssl is a set of OpenSSL bindings for the Rust programming language. In affected versions `ssl::select_next_proto` can return a slice pointing into the `server` argument&amp;#39;s buffer but with a lifetime bound to the `client` argument. In situations where the `sever` buffer&amp;#39;s lifetime is shorter than the `client` buffer&amp;#39;s, this can cause a use after free. This could cause the server to crash or to return arbitrary memory contents to the client. The crate`openssl` version 0.10.70 fixes the signature of `ssl::select_next_proto` to properly constrain the output buffer&amp;#39;s lifetime to that of both input buffers. Users are advised to upgrade. In standard usage of `ssl::select_next_proto` in the callback passed to `SslContextBuilder::set_alpn_select_callback`, code is only affected if the `server` buffer is constructed *within* the callback.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; sfackler rust-openssl&lt;/p&gt;
&lt;p&gt;rust-openssl is a set of OpenSSL bindings for the Rust programming language. In affected versions `ssl::select_next_proto` can return a slice pointing into the `server` argument&amp;#39;s buffer but with a lifetime bound to the `client` argument. In situations where the `sever` buffer&amp;#39;s lifetime is shorter than the `client` buffer&amp;#39;s, this can cause a use after free. This could cause the server to crash or to return arbitrary memory contents to the client. The crate`openssl` version 0.10.70 fixes the signature of `ssl::select_next_proto` to properly constrain the output buffer&amp;#39;s lifetime to that of both input buffers. Users are advised to upgrade. In standard usage of `ssl::select_next_proto` in the callback passed to `SslContextBuilder::set_alpn_select_callback`, code is only affected if the `server` buffer is constructed *within* the callback.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-24898</guid>
    </item>
    <item>
      <title>GHSA-rpmj-rpgj-qmpm — rust-openssl ssl::select_next_proto use after free</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-rpmj-rpgj-qmpm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: openssl&lt;/p&gt;
&lt;p&gt;### Impact
`ssl::select_next_proto` can return a slice pointing into the `server` argument&amp;#39;s buffer but with a lifetime bound to the `client` argument. In situations where the `server` buffer&amp;#39;s lifetime is shorter than the `client` buffer&amp;#39;s, this can cause a use after free. This could cause the server to crash or to return arbitrary memory contents to the client.&lt;/p&gt;
&lt;p&gt;### Patches
`openssl` 0.10.70 fixes the signature of `ssl::select_next_proto` to properly constrain the output buffer&amp;#39;s lifetime to that of both input buffers.&lt;/p&gt;
&lt;p&gt;### Workarounds
In standard usage of `ssl::select_next_proto` in the callback passed to `SslContextBuilder::set_alpn_select_callback`, code is only affected if the `server` buffer is constructed *within* the callback. For example:&lt;/p&gt;
&lt;p&gt;Not vulnerable - the server buffer has a `&amp;#39;static` lifetime:
```rust
builder.set_alpn_select_callback(|_, client_protos| {
    ssl::select_next_proto(b&amp;#34;\x02h2&amp;#34;, client_protos).ok_or_else(AlpnError::NOACK)
});
```&lt;/p&gt;
&lt;p&gt;Not vulnerable - the server buffer outlives the handshake:
```rust
let server_protos = b&amp;#34;\x02h2&amp;#34;.to_vec();
builder.set_alpn_select_callback(|_, client_protos| {
    ssl::select_next_proto(&amp;amp;server_protos, client_protos).ok_or_else(AlpnError::NOACK)
});
```&lt;/p&gt;
&lt;p&gt;Vulnerable - the server buffer is freed when the callback returns:
```rust
builder.set_alpn_select_callback(|_, client_protos| {
    let server_protos = b&amp;#34;\x02h2&amp;#34;.to_vec();
    ssl::select_next_proto(&amp;amp;server_protos, client_protos).ok_or_else(AlpnError::NOACK)
});
```…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: openssl&lt;/p&gt;
&lt;p&gt;### Impact
`ssl::select_next_proto` can return a slice pointing into the `server` argument&amp;#39;s buffer but with a lifetime bound to the `client` argument. In situations where the `server` buffer&amp;#39;s lifetime is shorter than the `client` buffer&amp;#39;s, this can cause a use after free. This could cause the server to crash or to return arbitrary memory contents to the client.&lt;/p&gt;
&lt;p&gt;### Patches
`openssl` 0.10.70 fixes the signature of `ssl::select_next_proto` to properly constrain the output buffer&amp;#39;s lifetime to that of both input buffers.&lt;/p&gt;
&lt;p&gt;### Workarounds
In standard usage of `ssl::select_next_proto` in the callback passed to `SslContextBuilder::set_alpn_select_callback`, code is only affected if the `server` buffer is constructed *within* the callback. For example:&lt;/p&gt;
&lt;p&gt;Not vulnerable - the server buffer has a `&amp;#39;static` lifetime:
```rust
builder.set_alpn_select_callback(|_, client_protos| {
    ssl::select_next_proto(b&amp;#34;\x02h2&amp;#34;, client_protos).ok_or_else(AlpnError::NOACK)
});
```&lt;/p&gt;
&lt;p&gt;Not vulnerable - the server buffer outlives the handshake:
```rust
let server_protos = b&amp;#34;\x02h2&amp;#34;.to_vec();
builder.set_alpn_select_callback(|_, client_protos| {
    ssl::select_next_proto(&amp;amp;server_protos, client_protos).ok_or_else(AlpnError::NOACK)
});
```&lt;/p&gt;
&lt;p&gt;Vulnerable - the server buffer is freed when the callback returns:
```rust
builder.set_alpn_select_callback(|_, client_protos| {
    let server_protos = b&amp;#34;\x02h2&amp;#34;.to_vec();
    ssl::select_next_proto(&amp;amp;server_protos, client_protos).ok_or_else(AlpnError::NOACK)
});
```…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-rpmj-rpgj-qmpm</guid>
    </item>
    <item>
      <title>RHSA-2025:7147 — security update for rpm-ostree</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2025:7147</link>
      <description>&lt;p&gt;security update for rpm-ostree&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;security update for rpm-ostree&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2025:7147</guid>
    </item>
  </channel>
</rss>
