Thursday, March 6, 2025
HomeCyber Security NewsBeyondTrust Zero-Day Breach - 17 SaaS Customers API Key Compromised

BeyondTrust Zero-Day Breach – 17 SaaS Customers API Key Compromised

Published on

SIEM as a Service

Follow Us on Google News

BeyondTrust, a leading provider of identity and access management solutions, disclosed a zero-day breach impacting 17 Remote Support SaaS customers.

The incident, detected on December 5, 2024, has been linked to the compromise of an infrastructure API key used to access specific Remote Support SaaS instances.

The breach allowed attackers to reset local application passwords in affected environments. Importantly, no BeyondTrust products outside of Remote Support SaaS were compromised, nor were its FedRAMP instances affected.

Details of the Breach

The breach originated from a zero-day vulnerability in a third-party application, which allowed attackers to access an online asset in BeyondTrust’s AWS account.

This asset contained an infrastructure API key, which was then used to access and exploit Remote Support SaaS environments.

BeyondTrust reported that no ransomware or unauthorized access has been detected since early December 2024, and no additional systems were compromised. To mitigate the impact, BeyondTrust swiftly:

  1. Revoked the compromised API key.
  2. Quarantined affected customer instances and offered replacement instances.
  3. Notified all affected customers.
  4. Partnered with federal law enforcement and a third-party forensic team for detailed investigations.

Timeline of the Incident

BeyondTrust’s swift response began immediately after detecting anomalous behavior on December 5, 2024.

The company initiated its incident response protocols, engaged a third-party forensic firm, and quarantined affected infrastructure. Key milestones include:

  • December 8, 2024: Initial security advisory published.
  • December 13, 2024: Discovery of two zero-day vulnerabilities, CVE-2024-12356 (critical) and CVE-2024-12686 (medium).
  • December 14-19, 2024: Vulnerabilities patched, with public disclosure and customer notifications following shortly after.
  • December 19, 2024: Law enforcement attributed the attack to China-linked threat actors.
  • January 17, 2025: BeyondTrust completed its forensics investigation.

To prevent future incidents, BeyondTrust recommends:

  • Staying up-to-date with patches and enabling auto-update features.
  • Using external authentication providers (e.g., SAML) over local accounts.
  • Employing outbound event notifications and SIEM integrations for monitoring suspicious activity.
  • Enforcing least-privilege access and rotating passwords regularly.

While BeyondTrust has taken exhaustive measures to secure its systems and assist affected customers, the company continues to work with law enforcement to track the threat actors responsible.

In a statement, BeyondTrust reaffirmed its commitment to transparency and enhanced cybersecurity, aiming to rebuild customer trust and strengthen its defenses.

Are you from SOC/DFIR Teams? – Analyse Malware Files & Links with ANY.RUN Sandox -> Start Now for Free.

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

Sitecore Zero-Day Flaw Allows Remote Code Execution

A critical zero-day vulnerability in Sitecore’s enterprise content management system (CMS) has been uncovered,...

Apache Airflow Misconfigurations Leak Login Credentials to Hackers

A recent investigation into misconfigured Apache Airflow instances has uncovered critical vulnerabilities exposing login...

Two Cybercriminals Arrested for ATM Jackpotting Scheme

Federal authorities have unveiled details of a sophisticated cybercrime operation targeting financial institutions across...

Black Basta’s Notorious Tactics and Techniques Exposed in Leaked Intel

A significant leak of internal chat logs from the Black Basta ransomware group has...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Sitecore Zero-Day Flaw Allows Remote Code Execution

A critical zero-day vulnerability in Sitecore’s enterprise content management system (CMS) has been uncovered,...

Apache Airflow Misconfigurations Leak Login Credentials to Hackers

A recent investigation into misconfigured Apache Airflow instances has uncovered critical vulnerabilities exposing login...

Two Cybercriminals Arrested for ATM Jackpotting Scheme

Federal authorities have unveiled details of a sophisticated cybercrime operation targeting financial institutions across...