https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 06:00:31 +0000 https://cve.radiocsirt.org/vuln/cve-2023-22794 <p><strong>Affected:</strong> https://github.com/rails/rails</p> <p>A vulnerability in ActiveRecord &lt;6.0.6.1, v6.1.7.1 and v7.0.4.1 related to the sanitization of comments. If malicious user input is passed to either the `annotate` query method, the `optimizer_hints` query method, or through the QueryLogs interface which automatically adds annotations, it may be sent to the database withinsufficient sanitization and be able to inject SQL outside of the comment.</p> <p><strong>Affected:</strong> https://github.com/rails/rails</p> <p>A vulnerability in ActiveRecord &lt;6.0.6.1, v6.1.7.1 and v7.0.4.1 related to the sanitization of comments. If malicious user input is passed to either the `annotate` query method, the `optimizer_hints` query method, or through the QueryLogs interface which automatically adds annotations, it may be sent to the database withinsufficient sanitization and be able to inject SQL outside of the comment.</p> https://cve.radiocsirt.org/vuln/cve-2023-22794 https://cve.radiocsirt.org/vuln/ghsa-hq7p-j377-6v63 <p><strong>Affected:</strong> RubyGems: activerecord</p> <p>There is a possible vulnerability in ActiveRecord related to the sanitization of comments. This vulnerability has been assigned the CVE identifier CVE-2023-22794.</p> <p>Versions Affected: &gt;= 6.0.0 Not affected: &lt; 6.0.0 Fixed Versions: 6.0.6.1, 6.1.7.1, 7.0.4.1 Impact</p> <p>Previously the implementation of escaping for comments was insufficient for</p> <p>If malicious user input is passed to either the annotate query method, the optimizer_hints query method, or through the QueryLogs interface which automatically adds annotations, it may be sent to the database with insufficient sanitization and be able to inject SQL outside of the comment.</p> <p>In most cases these interfaces won’t be used with user input and users should avoid doing so.</p> <p>Example vulnerable code: ``` Post.where(id: 1).annotate(&#34;#{params[:user_input]}&#34;)</p> <p>Post.where(id: 1).optimizer_hints(&#34;#{params[:user_input]}&#34;) ``` Example vulnerable QueryLogs configuration (the default configuration is not vulnerable): ``` config.active_record.query_log_tags = [ { something: -&gt; { &lt;some value including user input&gt; } } ] ``` All users running an affected release should either upgrade or use one of the workarounds immediately. Releases</p> <p>The FIXED releases are available at the normal locations. Workarounds</p> <p>Avoid passing user input to annotate and avoid using QueryLogs configuration which can include user input. Patches</p> <p>To aid users who aren’t able to upgrade immediately we have provided patches for the two supported release series. They a…</p> <p><strong>Affected:</strong> RubyGems: activerecord</p> <p>There is a possible vulnerability in ActiveRecord related to the sanitization of comments. This vulnerability has been assigned the CVE identifier CVE-2023-22794.</p> <p>Versions Affected: &gt;= 6.0.0 Not affected: &lt; 6.0.0 Fixed Versions: 6.0.6.1, 6.1.7.1, 7.0.4.1 Impact</p> <p>Previously the implementation of escaping for comments was insufficient for</p> <p>If malicious user input is passed to either the annotate query method, the optimizer_hints query method, or through the QueryLogs interface which automatically adds annotations, it may be sent to the database with insufficient sanitization and be able to inject SQL outside of the comment.</p> <p>In most cases these interfaces won’t be used with user input and users should avoid doing so.</p> <p>Example vulnerable code: ``` Post.where(id: 1).annotate(&#34;#{params[:user_input]}&#34;)</p> <p>Post.where(id: 1).optimizer_hints(&#34;#{params[:user_input]}&#34;) ``` Example vulnerable QueryLogs configuration (the default configuration is not vulnerable): ``` config.active_record.query_log_tags = [ { something: -&gt; { &lt;some value including user input&gt; } } ] ``` All users running an affected release should either upgrade or use one of the workarounds immediately. Releases</p> <p>The FIXED releases are available at the normal locations. Workarounds</p> <p>Avoid passing user input to annotate and avoid using QueryLogs configuration which can include user input. Patches</p> <p>To aid users who aren’t able to upgrade immediately we have provided patches for the two supported release series. They a…</p> https://cve.radiocsirt.org/vuln/ghsa-hq7p-j377-6v63