Monday, February 10, 2025
HomeCyber AttackMicrosoft Teams Vulnerability Let Attackers Deliver Malware From External Accounts

Microsoft Teams Vulnerability Let Attackers Deliver Malware From External Accounts

Published on

SIEM as a Service

Follow Us on Google News

The latest version of Microsoft Teams had a security flaw uncovered recently by Max Corbridge (@CorbridgeMax) and Tom Ellson (@tde_sec), JUMPSEC’s Red Team members.

Due to this flaw, there is a possibility for malware to be injected into organizations that rely on the default configuration of Microsoft Teams.

Microsoft Teams is used by over 280 million active users every month and is a popular way for organizations to talk and work together usin Microsoft 365.

Teams Vulnerability

Successful exploitation of this vulnerability enables the threat actors to evade the client-side security controls. This security feature prohibits users outside the organization from sending any file to the organization’s internal users.

Corbridge asserted in a report that the communication bridge they discovered is more vital because it can send harmful stuff straight to someone’s email, which is more potent than just tricking them.

Apart from this, two Jumpsec’s Red Team members uncovered a solution to circumvent the existing limitation.

They did this by altering the recipient ID in the POST request of a message for internal and external recipients, thereby tricking the system into recognizing an external user as an internal user.

In pragmatic trials, the researchers applied the technique. They successfully infiltrated a command and control payload into the inbox of a target organization, all while operating covertly as part of their red team exercise.

Attackers easily infect organizations using Microsoft Teams by bypassing security measures and anti-phishing training, exploiting the default configuration of it.

By registering a domain similar to the target’s Microsoft 365, the attacker can create messages that appear internal rather than external, increasing the chance of the target downloading the file without suspicion.

Response From Microsoft

Researchers notified Microsoft of their findings, expecting an immediate response due to the considerable impact observed.

Despite Microsoft acknowledging the flaw’s existence, its response indicated that it does not meet the threshold for immediate action, implying a lack of urgency to address the issue.

To minimize risk, organizations utilizing Microsoft Teams without requiring regular communication with external users should disable this feature. And to do this, you have to follow the simple steps that we have mentioned below:-

  • First of all, go to Microsoft Teams Admin Center.
  • Then access the External Access option.
  • After that, you must disable the chat with external unmanaged Teams users.

Organizations can establish an allow-list for specific domains to mitigate exploitation risks when maintaining external communication channels.

Manage and Secure Your Endpoints Efficiently – Free Download

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

Hackers Exploit AnyDesk Vulnerability to Gain Admin Access – PoC Released

A newly discovered vulnerability in AnyDesk, the popular remote desktop software, has sparked serious...

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...

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

Hackers Exploit AnyDesk Vulnerability to Gain Admin Access – PoC Released

A newly discovered vulnerability in AnyDesk, the popular remote desktop software, has sparked serious...

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...