Advisories

CVE-2024-29210

Title

CVE-2024-29210: Local Privilege Escalation via Configuration File Modification

Description

A local privilege escalation (LPE) vulnerability has been identified in three products, specifically within their configuration management functionalities. This vulnerability allows a regular user to modify the application's configuration file to redirect update checks to an arbitrary server, which can then be exploited in conjunction with CVE-2024-29209 to execute arbitrary code with elevated privileges.

The issue stems from improper permission settings on the application's configuration file, which is stored in a common directory accessible to all users. This file includes critical parameters, such as the update server URL. By default, the application does not enforce adequate access controls on this file, allowing non-privileged users to modify it without administrative consent.

An attacker with regular user access can alter the update server URL specified in the configuration file to point to a malicious server. When the application performs its next update check, it will contact the attacker-controlled server. If the system is also vulnerable to CVE-2024-29209, the attacker can deliver a malicious update package that, when executed, grants them elevated privileges.

Impact

This vulnerability can lead to a regular user executing code with administrative privileges. This can result in unauthorized access to sensitive data, installation of additional malware, and a full takeover of the affected system.

Affected Products

  • Phish Alert Button (PAB) for Outlook EXE versions 1.10.0-1.10.11
  • Second Chance Client versions 2.0.0-2.0.9
  • PIQ Client versions 1.0.0-1.0.15

Remediation

KnowBe4 has released a patch that corrects the permission settings on the configuration file to prevent unauthorized modifications. Automated updates will be pushed to address this issue. Users of affected versions should verify the latest version is applied and, if not, apply the latest updates provided by KnowBe4.

Workarounds

  • Manually set the correct permissions on the configuration file to restrict write access to administrators only.

Credits

This vulnerability was discovered by Ceri Coburn at Pen Test Partners, who reported it responsibly to the vendor.

Can't find what you're looking for?

Contact Support