Skip to content

dde-api-proxy: Privilege Escalation via Improper Proxying in Deepin D-Bus API-Proxy

Low
UTsweetyfish published GHSA-mpg5-wr29-xf8f Feb 3, 2026

Package

dde-api-proxy

Affected versions

>= 1.0.19

Patched versions

None

Description

Upstream published a bugfix here:

martyr-deepin/dde-api-proxy@95b50dd

This adds additional Polkit authorization within the proxy service for a list of manually maintained D-Bus methods. The checkAuthorization() method uses Polkit in an unsafe way, though:

        auto pid = connection.interface()->servicePid(service).value();
        auto authority = PolkitQt1::Authority::instance();
        auto result = authority->checkAuthorizationSync(actionId,
                                                        PolkitQt1::UnixProcessSubject(pid),
                                                        PolkitQt1::Authority::AllowUserInteraction);

Using the caller's PID for authentication poses a race condition that can again lead to a local root exploit.

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:N

CVE ID

No known CVE

Weaknesses

No CWEs