CVE Vulnerability Catalog

Tanium addressed a denial of service vulnerability in Tanium Server. It may lead to service unavailability.

Tanium addressed an uncontrolled resource consumption vulnerability in Performance Client Extension. Excessive consumption of system resources may occur.

Tanium addressed a SQL injection vulnerability in Patch. It may allow injection of malicious SQL code.

Tanium addressed a heap-based buffer overflow vulnerability in Index. The buffer overflow may lead to memory corruption and potential code execution.

Tanium addressed a local privilege escalation vulnerability in End-User Notifications. The flaw may allow a local user to gain higher privileges on the system.

Tanium addressed a local privilege escalation vulnerability in End-User Notifications. The flaw may allow a local user to gain higher privileges on the system.

Tanium addressed a local privilege escalation vulnerability in End-User Notifications. The flaw may allow a local user to gain higher privileges on the system.

Tanium addressed an unauthorized code execution vulnerability in Certificate Manager. Technical details were not disclosed in the description.

Tanium addressed an improper access controls vulnerability in Comply. It may allow access to functions or data without required permissions.

Tanium addressed an improper access controls vulnerability in Comply. The flaw allowed bypassing authorization mechanisms within this component.

An authorization vulnerability exists in the country or region configuration interface of TP-Link RE305 V3. An unauthenticated attacker on the same local network may modify the wireless regulatory region and force the device to reapply its wireless configuration.

An operating-system command injection vulnerability exists in the tmpServer service of TP-Link RE305 V3. The service runs with root privileges and listens on the local loopback interface; a local attacker with access to a low-privileged process may submit a crafted request to the TDDPv1 service and execute OS commands with root privileges.

An authentication weakness exists in the TP-Link TDDP v2 service of TP-Link RE305 V3, which uses a fixed and derivable cryptographic key. An unauthenticated attacker on the same local network may forge protocol packets and access privileged TDDP operations, including functionality that can lead to operating-system command execution.

An authentication flaw exists in the password-recovery functionality of TP-Link RE305 V3. The verification-code interface allows an unauthenticated attacker on the same local network to trigger generation of an administrator password-reset verification code; the lack of an effective attempt counter or lockout and a predictable code generation process may allow obtaining or brute-forcing the code.

A hard-coded cryptographic key vulnerability exists in the user-configuration backup mechanism of TP-Link RE305 V3 and Archer C7 V5. A fixed AES-128 key and initialization vector are embedded in the firmware configuration-management component; an attacker who obtains an affected backup file may extract the cryptographic material from the firmware and decrypt the backup.

An SSRF vulnerability allows access to internal Chrome DevTools Protocol APIs, which can leak the JWT authentication token of another user. A low-privileged attacker could repeatedly exploit this when starting a recording to obtain the victim's JWT token, gaining read/write access to the victim's Whiteboard.

A user in a group can bypass the link-sharing restriction set by an administrator and create share links for a table despite lacking that permission.

When a team was configured as "visible to everyone", the web UI correctly blocked non-members, but the resources API endpoint could still be called directly. This allowed any authenticated non-member to enumerate the team's internal resources and their identifiers.

The Tables app's share-listing endpoint (GET /apps/tables/share/table/{tableId}) did not verify that the requesting user has manage-level permission on the table before returning the full list of share recipients (users, groups, and teams) along with their permission levels. A user granted only read-data access could call the endpoint directly to enumerate everyone the table is shared with and their access levels.

A user could create a docx or odt file with a # in the filename containing confidential information such as a credit card number, and the file would not be marked as confidential.