Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-10941: Permission Issues in Topaz SERVCore Teller

0
High
VulnerabilityCVE-2025-10941cvecve-2025-10941
Published: Thu Sep 25 2025 (09/25/2025, 11:02:05 UTC)
Source: CVE Database V5
Vendor/Project: Topaz
Product: SERVCore Teller

Description

A vulnerability was determined in Topaz SERVCore Teller 2.14.0-RC2/2.14.1. Affected by this issue is some unknown functionality of the file SERVCoreTeller_2.0.40D.msi of the component Installer. Executing manipulation can lead to permission issues. The attack needs to be launched locally. You should upgrade the affected component. The vendor explains, that "this vulnerability was detected at the beginning of 2025, it was remediated because the latest published version of the installer no longer uses "nssm," which is responsible for this vulnerability".

AI-Powered Analysis

AILast updated: 10/03/2025, 00:27:07 UTC

Technical Analysis

CVE-2025-10941 is a high-severity vulnerability identified in Topaz SERVCore Teller versions 2.14.0-RC2 and 2.14.1, specifically related to the Installer component within the SERVCoreTeller_2.0.40D.msi file. The vulnerability arises from permission issues caused by the use of "nssm" (Non-Sucking Service Manager), a service manager utility that was part of the installer. This flaw allows a local attacker with limited privileges (low-level privileges) to manipulate the installer in a way that escalates permissions, potentially granting higher access rights than intended. The attack requires local access to the affected system, meaning remote exploitation is not feasible without prior access. The vendor has addressed this vulnerability by removing the dependency on "nssm" in the latest installer versions, effectively mitigating the issue. The CVSS 4.0 base score of 8.5 reflects the high impact on confidentiality, integrity, and availability, with low attack complexity and no user interaction required. However, the vulnerability does not require elevated privileges to initiate but does require local access, limiting the attack vector to insiders or users with some system access. No known exploits are currently reported in the wild, but the potential for privilege escalation makes this a significant risk in environments where SERVCore Teller is deployed.

Potential Impact

For European organizations using Topaz SERVCore Teller, particularly in financial or banking sectors where this software is likely deployed, this vulnerability poses a significant risk. An attacker with local access could exploit the permission issues to escalate privileges, potentially gaining unauthorized access to sensitive financial data or critical system functions. This could lead to data breaches, manipulation of transaction records, or disruption of teller operations. The impact on confidentiality is high due to possible unauthorized data access; integrity is at risk because of potential unauthorized modifications; and availability could be affected if the attacker disrupts service components. Given the local attack vector, insider threats or compromised endpoints within the organization's network are the primary concern. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially in environments with less stringent internal access controls.

Mitigation Recommendations

European organizations should prioritize upgrading to the latest version of the SERVCore Teller installer that no longer uses "nssm" to eliminate this vulnerability. In addition, organizations should enforce strict local access controls and monitoring to detect and prevent unauthorized local access attempts. Implementing endpoint security solutions that can detect privilege escalation attempts and anomalous installer manipulations is recommended. Regular audits of user permissions and system logs can help identify suspicious activities early. Network segmentation to isolate teller systems and restrict access to only authorized personnel will reduce the attack surface. Since the vulnerability requires local access, strengthening physical security and endpoint hardening measures is critical. Finally, organizations should maintain an incident response plan tailored to privilege escalation incidents to respond swiftly if exploitation is suspected.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
VulDB
Date Reserved
2025-09-25T05:44:37.750Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68d523a21c4cbdeab7737b7c

Added to database: 9/25/2025, 11:12:34 AM

Last enriched: 10/3/2025, 12:27:07 AM

Last updated: 11/7/2025, 5:58:01 AM

Views: 44

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats