Dikai Zou

Authenticated users can access resources belonging to other users because object-level authorization checks are omitted on REST endpoints related to geographic information, dashboard linkage, and chart detail. By supplying arbitrary identifiers in requests, attackers can overwrite or delete map geometry, modify dashboard linkages, and retrieve chart metadata and configuration for resources they do not own.

Multiple access control defects exist in the sharing link module. A valid ticket issued for one share can be reused against another because tickets are not bound to the target share UUID, affecting the `ShareTicketManage.validateTicket()` function at the 'POST /de2api/share/proxyInfo' endpoint. The 'POST /de2api/share/validate' endpoint allows the issuance of a LinkToken after password verification without requiring a ticket, bypassing the mandatory ticket policy. Furthermore, the 'POST /de2api/ticket/saveTicket' and 'POST /de2api/ticket/delTicket' endpoints lack share-ownership checks, enabling authenticated users to modify, rebind, or delete tickets belonging to others, which can lead to a denial of service. Additionally, the 'GET /de2api/share/queryRelationByUserId/{uid}' endpoint allows authenticated users to enumerate share mappings of other users via the `uid` variable.

Partial-chain certificate verification may accept chains that terminate at a peer-supplied, untrusted intermediate certificate instead of a trusted anchor. This allows an attacker to present a chain ending at an intermediate certificate they control and have it accepted as valid. This issue occurs in the OpenSSL compatibility certificate-path-building path using the `wolfSSL X509 verify cert()` function and `X509 STORE` when the `X509 V FLAG PARTIAL CHAIN` verify flag is enabled.

A heap buffer overread occurs in the `wc PKCS7 DecodeEnvelopedData()` function when parsing specially crafted PKCS7 EnvelopedData. This issue could be triggered by attacker-supplied data delivered via S/MIME (Secure/Multipurpose Internet Mail Extensions) or CMS (Cryptographic Message Syntax).

An integer underflow occurs in the `wc PKCS7 DecryptOri()` function when processing specially crafted Other Recipient Info. This leads to incorrect length handling during the decryption process.

An issue exists where SNI (Server Name Indication) and ALPN (Application-Layer Protocol Negotiation) bindings are missing during stateful session-ID resumption. This allows a cached session to be resumed using a different SNI or ALPN than what was originally negotiated. In environments where client-authentication policies vary across virtual hosts, this could allow a cached peer-authentication state to be applied to a context for which it was not intended.

An authorization bypass exists in the bundled device-pair plugin. This issue allows non-owner authorized chat senders to issue device-pairing bootstrap codes because the system fails to perform proper scope validation. Attackers with chat command access can generate setup codes to enroll devices with operator or node capabilities, which provides them with persistent credentials until the devices are manually removed.

A privilege escalation issue exists in Slack plugin approvals. This allows users with exec-authorized permissions to resolve plugin approvals via the exec approver gate, enabling them to bypass intended approval splits and approve plugin actions that fall outside the operator configuration.

A policy bypass exists in QQBot admin commands. This issue allows authenticated senders to circumvent `DM-only` and `allowFrom` policy checks. Consequently, attackers can route admin commands from unauthorized senders or contexts to execute restricted behaviors that the policy was intended to block.

An authorization bypass exists in the QQBot native approval buttons. The button callback path fails to enforce the configured approver identity, allowing users who are not authorized approvers to click approval buttons and resolve pending exec or plugin approval requests. This issue is specific to native QQBot approval buttons and does not affect the text command approval path. This occurs in deployments where native approval buttons are enabled and visible to unauthorized QQ users.

A Server-Side Request Forgery (SSRF) policy bypass exists in the browser debug and export routes. This issue allows the reuse of already-open blocked tabs, enabling attackers with access to these routes to bypass private-network SSRF policies. Consequently, they can export or inspect content that is intended to remain protected.

A scope bypass exists in the Gateway 'chat.send' endpoint. This issue allows clients with the `operator.write` scope to execute privileged commands by utilizing inherited external routes. This bypass circumvents the requirements for `operator.approvals` and `operator.admin` scopes, enabling unauthorized mutations of plugins, configurations, MCP, allowlists, and ACP.