Synopsis
CVE-2025-40795 um.Ris.exe Message 17 Stack-based Buffer Overflow (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
An unauthenticated, remote attacker can send a crafted message to cause a stack-based buffer overflow.
CVE-2025-40796 um.Ris.exe Out-of-bounds Read DoS (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
An unauthenticated, remote attacker can send a partial message causing an invalid memory access and crash in um.Ris.exe.
CVE-2025-40797 um.Ris.exe Message 3 Out-of-bounds Read DoS (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
An unauthenticated, remote attacker can send an integer with a large value to crash um.Ris.exe.
CVE-2025-40798 um.Ris.exe Message 4 Out-of-bounds Read DoS (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
An unauthenticated, remote attacker can send an integer with a large value to crash um.Ris.exe.
Solution
Update UMC to V2.15.1.3 or later compatible version.
Siemens also provides the following workarounds: In non-networked scenarios/deployments block TCP ports 4002 and 4004 on machines with UMC installed. If the deployment is not using the 'RT Server' type of UMC machine, port 4004 can be blocked everywhere without impacting network functionality for all other UMC machine-types (Server, Ring-Server, Agent).
Disclosure Timeline
All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.
Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.
For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.
If you have questions or corrections about this advisory, please email [email protected]