CVE-2025-23222
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-23222 is a high-severity Improper Verification of Source of a Communication Channel (CWE-940) vulnerability in Suse (inferred from references). Its CVSS base score is 8.4 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique ARP Cache Poisoning (T1557.002); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-17 (Remote Access) and IA-3 (Device Identification and Authentication) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-23222 is a privilege escalation vulnerability affecting Deepin dde-api-proxy through version 1.0.19. The dde-api-proxy runs as root and forwards D-Bus messages from arbitrary local unprivileged users to legacy D-Bus methods in actual D-Bus services. These services are unaware of the proxy and treat the requests as originating from root, enabling unprivileged users to access proxied methods that should be restricted to root. When Polkit is involved, the caller is treated as an admin, resulting in privilege escalation. The issue carries a CVSS v3.1 base score of 8.4 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and is associated with CWE-940.
The vulnerability can be exploited by local unprivileged attackers requiring no special privileges. By sending crafted messages through the dde-api-proxy, attackers can invoke privileged D-Bus methods, achieving high impacts on confidentiality, integrity, and availability, effectively escalating privileges to root or admin levels.
Advisories addressing CVE-2025-23222 include the SUSE Bugzilla entry at https://bugzilla.suse.com/show_bug.cgi?id=1229918, the openSUSE security notice at https://security.opensuse.org/2025/01/24/dde-api-proxy-privilege-escalation.html, and the OSS-Security mailing list discussion at https://www.openwall.com/lists/oss-security/2025/01/24/3.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-3151
Vulnerability Data
An issue was discovered in Deepin dde-api-proxy through 1.0.19 in which unprivileged users can access D-Bus services as root. Specifically, dde-api-proxy runs as root and forwards messages from arbitrary local users to legacy D-Bus methods in the actual D-Bus services,…
more
and the actual D-Bus services don't know about the proxy situation (they believe that root is asking them to do things). Consequently several proxied methods, that shouldn't be accessible to non-root users, are accessible to non-root users. In situations where Polkit is involved, the caller would be treated as admin, resulting in a similar escalation of privileges.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.5.3V10.6.2V15.2.4
Mitigating Controls (NIST 800-53 r5) AI
IA-3 requires unique identification and authentication of devices before any communication channel is established, directly stopping acceptance of unverified origins.
AC-17 mandates documented restrictions and authentication requirements for remote access, blocking channels whose origins are not properly verified.
SC-23 protects session authenticity, ensuring the source of an established communication channel is verified and cannot be spoofed.
SC-7 enforces monitoring and control at external and key internal interfaces, preventing channels from unverified sources via boundary rules.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Authentication of users/services/hardware directly enforces source verification for communication channels.
Verifying identity assertions prevents spoofed channel origins but does not cover all channel-establishment scenarios.
Network protections reduce unauthorized channel usage but do not specifically require origin verification at channel setup.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure authentication mechanisms verify the identity and origin of communication channel initiators.
Network security controls enforce source verification and channel authentication for incoming communications.
Security of network services includes validating the origin of service requests and connections.
Network segregation limits exposure but does not directly verify source of individual channels.
Cryptography can support channel authentication but does not inherently verify source without proper implementation.
Application security requirements may specify origin checks but do not mandate them.