<?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>Tue, 06 Oct 2026 22:27:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-31162 — Slack Morphism for Rust before 0.41.0 can accidentally leak Slack OAuth client information in application debug logs</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-31162</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; abdolence slack-morphism-rust&lt;/p&gt;
&lt;p&gt;Slack Morphism is an async client library for Rust. Prior to 0.41.0, it was possible for Slack OAuth client information to leak in application debug logs. Stricter and more secure debug formatting was introduced in v0.41.0 for OAuth secret types to reduce the possibility of printing sensitive information in application logs. As a workaround, do not print/output requests and responses for OAuth and client configurations in logs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; abdolence slack-morphism-rust&lt;/p&gt;
&lt;p&gt;Slack Morphism is an async client library for Rust. Prior to 0.41.0, it was possible for Slack OAuth client information to leak in application debug logs. Stricter and more secure debug formatting was introduced in v0.41.0 for OAuth secret types to reduce the possibility of printing sensitive information in application logs. As a workaround, do not print/output requests and responses for OAuth and client configurations in logs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-31162</guid>
    </item>
    <item>
      <title>GHSA-99j7-mhfh-w84p — Slack Morphism for Rust before 0.41.0 can leak Slack OAuth client information in application debug logs</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-99j7-mhfh-w84p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: slack-morphism&lt;/p&gt;
&lt;p&gt;### Impact
Potential/accidental leaking of Slack OAuth client information in application debug logs.&lt;/p&gt;
&lt;p&gt;### Patches
More strict and secure debug formatting was introduced in v0.41 for OAuth secret types to avoid the possibility of printing sensitive information in application logs.&lt;/p&gt;
&lt;p&gt;### Workarounds
Don&amp;#39;t print/output in logs request and responses for OAuth and client configurations.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [repo](https://github.com/abdolence/slack-morphism-rust)
* Email us at [me@abdolence.dev](mailto:me@abdolence.dev)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: slack-morphism&lt;/p&gt;
&lt;p&gt;### Impact
Potential/accidental leaking of Slack OAuth client information in application debug logs.&lt;/p&gt;
&lt;p&gt;### Patches
More strict and secure debug formatting was introduced in v0.41 for OAuth secret types to avoid the possibility of printing sensitive information in application logs.&lt;/p&gt;
&lt;p&gt;### Workarounds
Don&amp;#39;t print/output in logs request and responses for OAuth and client configurations.&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in the [repo](https://github.com/abdolence/slack-morphism-rust)
* Email us at [me@abdolence.dev](mailto:me@abdolence.dev)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-99j7-mhfh-w84p</guid>
    </item>
  </channel>
</rss>
