CVE-2025-57141
BaseFortify
Publication date: 2025-09-08
Last updated on: 2025-09-12
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ruisitech | ruisibi | 4.7 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-57141 is a remote code execution (RCE) vulnerability in rsbi version 4.7 related to unsafe deserialization in the MySQL JDBC driver. When the JDBC connection URL includes the parameter 'autoDeserialize=true', malicious MySQL server responses can trigger unsafe deserialization processes. This allows attackers to execute arbitrary code remotely by sending specially crafted requests that exploit this deserialization flaw. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to remotely execute arbitrary code on a server running rsbi 4.7 with the vulnerable JDBC configuration. This could lead to full system compromise, data theft, data corruption, or disruption of services, as the attacker gains control over the affected system through the unsafe deserialization process. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking if the rsbi 4.7 system is using a MySQL JDBC connection URL with the parameter `autoDeserialize=true`. For example, inspect configuration files or logs for JDBC URLs containing `autoDeserialize=true`. Additionally, monitor network traffic for POST requests to the endpoint `/rsbi/model/testDataSource.action` that include suspicious payloads. A command to search configuration files for the vulnerable parameter could be: `grep -r 'autoDeserialize=true' /path/to/rsbi/config/`. Network traffic can be inspected using tools like tcpdump or Wireshark filtering for POST requests to `/rsbi/model/testDataSource.action`. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling the `autoDeserialize=true` parameter in the MySQL JDBC connection URL used by rsbi 4.7 to prevent unsafe deserialization. If possible, update or patch rsbi to a version that addresses this vulnerability. Additionally, restrict access to the `/rsbi/model/testDataSource.action` endpoint to trusted users or networks to reduce exposure. Monitoring and blocking suspicious POST requests targeting this endpoint can also help mitigate exploitation attempts. [1]