Cyber

What changed

BeyondTrust has addressed a critical security flaw in its Remote Support software, which has been under active exploitation since late August. The company has urged all users to implement the patch immediately to mitigate potential risks.

• The vulnerability is classified as a zero-day, indicating it was exploited before a fix was available.
• Users of the affected software are at risk of unauthorized access and potential data breaches.
• The patch is now available for immediate deployment to secure systems.

Who is affected

Organizations utilizing BeyondTrust Remote Support are directly impacted by this vulnerability. It is crucial for these entities to prioritize patching to safeguard their systems.

• BeyondTrust Remote Support users across various sectors.
• IT departments managing remote support solutions.
• Organizations with sensitive data that rely on remote access tools.
• Any third-party vendors integrating BeyondTrust solutions.

What to do

Immediate action is required to patch the vulnerability in BeyondTrust Remote Support. Organizations should ensure that their systems are updated to the latest version as soon as possible.

• Review and apply the latest security patches provided by BeyondTrust.
• Monitor systems for any unusual activity that may indicate exploitation.
• Educate staff on the importance of timely updates and security practices.
• Consider conducting a security audit to assess the overall risk posture.

What changed

A local privilege escalation vulnerability has been identified in the FreeBSD Kernel, specifically a Time-Of-Check Time-Of-Use (TOCTOU) issue. This flaw enables local attackers to escalate their privileges on affected systems, potentially leading to unauthorized access and control.

The vulnerability has been assigned a CVSS score of 7.8, indicating a high severity level, which necessitates prompt attention from system administrators.

Who is affected

This vulnerability affects installations of the FreeBSD Kernel, which is widely used in various environments, including servers and embedded systems.

Organizations utilizing FreeBSD in their infrastructure should be particularly vigilant.

• FreeBSD Kernel installations across various versions
• Organizations relying on FreeBSD for server operations
• Developers deploying applications on FreeBSD systems

What to do

System administrators are advised to assess their FreeBSD installations for exposure to this vulnerability. Immediate action should be taken to apply any available patches or mitigations.

Regularly monitor security advisories from FreeBSD and related security platforms to stay informed about updates and fixes.

• Review system logs for any unauthorized access attempts
• Implement strict access controls to limit execution of low-privileged code
• Stay updated with the latest security patches from FreeBSD