<?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, 16 Oct 2026 20:01:43 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-232589</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-232589</link>
      <description>EUVD-2026-232589</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-232589</guid>
    </item>
    <item>
      <title>fkie_cve-2022-39312</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-39312</link>
      <description>&lt;p&gt;Dataease is an open source data visualization analysis tool. Dataease prior to 1.15.2 has a deserialization vulnerability. In Dataease, the Mysql data source in the data source function can customize the JDBC connection parameters and the Mysql server target to be connected. In `backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java`, the `MysqlConfiguration` class does not filter any parameters. If an attacker adds some parameters to a JDBC url and connects to a malicious mysql server, the attacker can trigger the mysql jdbc deserialization vulnerability. Through the deserialization vulnerability, the attacker can execute system commands and obtain server privileges. Version 1.15.2 contains a patch for this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Dataease is an open source data visualization analysis tool. Dataease prior to 1.15.2 has a deserialization vulnerability. In Dataease, the Mysql data source in the data source function can customize the JDBC connection parameters and the Mysql server target to be connected. In `backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java`, the `MysqlConfiguration` class does not filter any parameters. If an attacker adds some parameters to a JDBC url and connects to a malicious mysql server, the attacker can trigger the mysql jdbc deserialization vulnerability. Through the deserialization vulnerability, the attacker can execute system commands and obtain server privileges. Version 1.15.2 contains a patch for this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-39312</guid>
    </item>
    <item>
      <title>GHSA-q4qq-jhjv-7rh2 — MySQL JDBC deserialization vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q4qq-jhjv-7rh2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.dataease:dataease-plugin-common&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In Dataease, the Mysql data source in the data source function can customize the JDBC connection parameters and the Mysql server target to be connected.
![6fc8d5c539807157ee471464b184ab66](https://user-images.githubusercontent.com/13026505/195741851-19f32efb-4391-428a-949f-3d11849f417a.png)&lt;/p&gt;
&lt;p&gt;In `backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java`, MysqlConfiguration class don&amp;#39;t filter any parameters, directly concat user input.
```java
@Getter
@Setter
public class MysqlConfiguration extends JdbcConfiguration {&lt;/p&gt;
&lt;p&gt;private String driver = &amp;#34;com.mysql.jdbc.Driver&amp;#34;;
    private String extraParams = &amp;#34;characterEncoding=UTF-8&amp;amp;connectTimeout=5000&amp;amp;useSSL=false&amp;amp;allowPublicKeyRetrieval=true&amp;amp;zeroDateTimeBehavior=convertToNull&amp;#34;;&lt;/p&gt;
&lt;p&gt;public String getJdbc() {
        if(StringUtils.isEmpty(extraParams.trim())){
            return &amp;#34;jdbc:mysql://HOSTNAME:PORT/DATABASE&amp;#34;
                    .replace(&amp;#34;HOSTNAME&amp;#34;, getHost().trim())
                    .replace(&amp;#34;PORT&amp;#34;, getPort().toString().trim())
                    .replace(&amp;#34;DATABASE&amp;#34;, getDataBase().trim());
        }else {
            return &amp;#34;jdbc:mysql://HOSTNAME:PORT/DATABASE?EXTRA_PARAMS&amp;#34;
                    .replace(&amp;#34;HOSTNAME&amp;#34;, getHost().trim())
                    .replace(&amp;#34;PORT&amp;#34;, getPort().toString().trim())
                    .replace(&amp;#34;DATABASE&amp;#34;, getDataBase().trim())
                    .replace(&amp;#34;EXTRA_PARAMS&amp;#34;, getExtraParams().trim());
        }
    }
}
```
So, if the attack add some parameters in J…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: io.dataease:dataease-plugin-common&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In Dataease, the Mysql data source in the data source function can customize the JDBC connection parameters and the Mysql server target to be connected.
![6fc8d5c539807157ee471464b184ab66](https://user-images.githubusercontent.com/13026505/195741851-19f32efb-4391-428a-949f-3d11849f417a.png)&lt;/p&gt;
&lt;p&gt;In `backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java`, MysqlConfiguration class don&amp;#39;t filter any parameters, directly concat user input.
```java
@Getter
@Setter
public class MysqlConfiguration extends JdbcConfiguration {&lt;/p&gt;
&lt;p&gt;private String driver = &amp;#34;com.mysql.jdbc.Driver&amp;#34;;
    private String extraParams = &amp;#34;characterEncoding=UTF-8&amp;amp;connectTimeout=5000&amp;amp;useSSL=false&amp;amp;allowPublicKeyRetrieval=true&amp;amp;zeroDateTimeBehavior=convertToNull&amp;#34;;&lt;/p&gt;
&lt;p&gt;public String getJdbc() {
        if(StringUtils.isEmpty(extraParams.trim())){
            return &amp;#34;jdbc:mysql://HOSTNAME:PORT/DATABASE&amp;#34;
                    .replace(&amp;#34;HOSTNAME&amp;#34;, getHost().trim())
                    .replace(&amp;#34;PORT&amp;#34;, getPort().toString().trim())
                    .replace(&amp;#34;DATABASE&amp;#34;, getDataBase().trim());
        }else {
            return &amp;#34;jdbc:mysql://HOSTNAME:PORT/DATABASE?EXTRA_PARAMS&amp;#34;
                    .replace(&amp;#34;HOSTNAME&amp;#34;, getHost().trim())
                    .replace(&amp;#34;PORT&amp;#34;, getPort().toString().trim())
                    .replace(&amp;#34;DATABASE&amp;#34;, getDataBase().trim())
                    .replace(&amp;#34;EXTRA_PARAMS&amp;#34;, getExtraParams().trim());
        }
    }
}
```
So, if the attack add some parameters in J…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q4qq-jhjv-7rh2</guid>
    </item>
    <item>
      <title>gsd-2022-39312</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-39312</link>
      <description>gsd-2022-39312</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-39312</guid>
    </item>
  </channel>
</rss>
