Overview
The vulnerability CVE-2025-22956 poses a significant threat to systems running versions of OPSI before 4.3. This issue allows any client to access other clients’ ProductPropertyStates, potentially leading to privilege escalation. If a ProductPropertyState contains a secret that should be accessible only to a specific subset of clients, this flaw may expose it to unauthorized users. For instance, a domain join account password for the windomain package.
This is a serious concern because it can enable unauthorized users to gain elevated privileges, leading to potential system compromise or data leakage. Therefore, it is crucial that organizations using the affected versions of OPSI take immediate steps to mitigate this vulnerability.
Vulnerability Summary
CVE ID: CVE-2025-22956
Severity: Critical (9.8)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Privilege escalation, potential system compromise, and data leakage
Affected Products
Share secrets securely
Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.
Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.
- • Encrypted identity
- • Private Spaces for organizations and teams
- • End-to-end encrypted chat, calls, files, and notes
- • Sensitive AI work and protected collaboration
- • Built for information that cannot leak
Our mission is to secure human work alongside AI.
Product | Affected Versions
OPSI | Before 4.3
How the Exploit Works
An attacker exploiting this vulnerability would send a request to the OPSI server with the intention to retrieve the ProductPropertyState of another client. Since the server does not adequately validate the request, it can return sensitive data, including secrets associated with other clients’ ProductPropertyStates. The attacker can then use these secret credentials to escalate their privileges.
Conceptual Example Code
Here’s a conceptual example of how the vulnerability might be exploited using an HTTP request:
GET /opsi-api/v1/ProductPropertyState/{Client_ID} HTTP/1.1
Host: target.example.com
Content-Type: application/json
Authorization: Bearer {Attacker_token}In this example, the attacker sends a GET request to the OPSI server to retrieve the ProductPropertyState associated with another client’s ID (represented by `{Client_ID}`). The server does not verify whether the requestor has the necessary privileges to access this information, leading to unauthorized access and potential privilege escalation.
Mitigation
Users are advised to apply the vendor patch to correct this flaw as soon as it’s available. As a temporary mitigation measure, users may consider deploying a Web Application Firewall (WAF) or an Intrusion Detection System (IDS) to detect and block unauthorized requests. Additionally, review the access controls and ensure that they are properly configured to restrict access to sensitive information.