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-67813: n/a

0
Medium
VulnerabilityCVE-2025-67813cvecve-2025-67813
Published: Mon Jan 12 2026 (01/12/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

Quest KACE Desktop Authority through 11.3.1 has Insecure Permissions on the Named Pipes used for inter-process communication

AI-Powered Analysis

AILast updated: 01/12/2026, 16:08:04 UTC

Technical Analysis

CVE-2025-67813 identifies a security vulnerability in Quest KACE Desktop Authority versions up to 11.3.1, where the named pipes used for inter-process communication (IPC) have insecure permissions. Named pipes are a Windows IPC mechanism allowing processes to communicate, often used by system management tools like Quest KACE Desktop Authority to coordinate tasks and exchange sensitive information. Insecure permissions on these pipes mean that unauthorized local users or processes could potentially access or manipulate the data transmitted through these channels. This could lead to privilege escalation, unauthorized command execution, or leakage of sensitive configuration or credential information. The vulnerability does not require remote network access but does require local access to the affected system, which could be achieved through compromised user accounts or insider threats. No CVSS score has been assigned yet, and no public exploits are known, but the issue is significant due to the sensitive nature of IPC in endpoint management software. The lack of patch links suggests that a fix may not yet be publicly available, emphasizing the need for immediate mitigation steps such as permission audits and restricting local user privileges. Organizations relying on Quest KACE Desktop Authority for endpoint management should be vigilant, as exploitation could undermine the integrity and confidentiality of their IT management operations.

Potential Impact

For European organizations, this vulnerability could compromise the confidentiality and integrity of endpoint management operations. Unauthorized local access to named pipes may allow attackers to escalate privileges, execute unauthorized commands, or intercept sensitive data such as credentials or configuration details. This could lead to broader network compromise, disruption of IT management workflows, and potential data breaches. Organizations in sectors with strict regulatory requirements (e.g., finance, healthcare, critical infrastructure) could face compliance violations and reputational damage if exploited. The impact is particularly concerning for enterprises with large deployments of Quest KACE Desktop Authority, as a single compromised endpoint could serve as a foothold for lateral movement within the network. Although remote exploitation is not possible, the threat from insider attackers or malware that gains local access remains significant. The absence of known exploits provides a window for proactive mitigation, but the risk remains high due to the critical role of the affected software in managing enterprise endpoints.

Mitigation Recommendations

1. Immediately audit and tighten the permissions on named pipes used by Quest KACE Desktop Authority to ensure only authorized system processes and administrators have access. 2. Restrict local user privileges to the minimum necessary to prevent unauthorized access to IPC mechanisms. 3. Monitor local system logs and IPC activity for unusual access patterns or unauthorized attempts to interact with named pipes. 4. Implement endpoint detection and response (EDR) solutions capable of detecting suspicious local process interactions. 5. Segregate management consoles and servers from general user workstations to limit exposure. 6. Stay informed about official patches or updates from Quest and apply them promptly once available. 7. Conduct regular security awareness training to reduce insider threat risks. 8. Consider application whitelisting to prevent unauthorized processes from running and accessing IPC channels. 9. Use host-based firewalls and access control lists to limit local network communication where feasible. 10. Prepare incident response plans that include scenarios involving local privilege escalation and IPC exploitation.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-12-12T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69651909da2266e838cc4bff

Added to database: 1/12/2026, 3:53:45 PM

Last enriched: 1/12/2026, 4:08:04 PM

Last updated: 1/12/2026, 11:28:35 PM

Views: 9

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats