Advisor
Wiki Techniques, Tactics & Procedures (TTPs) Persistence OAuth Application Abuse

OAuth Application Abuse

2 min read
Jump to:

Overview

OAuth Application Abuse involves adversaries exploiting OAuth authorization flows to gain unauthorized access to resources or escalate privileges within a target environment. This technique is leveraged at various stages of the attack lifecycle to bypass traditional authentication controls and maintain persistence or access sensitive data.

Attack Objective

  • Gain unauthorized access to user or application resources
  • Support stages including Initial Access, Persistence, Privilege Escalation, and Defense Evasion
  • Advance attacker position by leveraging legitimate authorization tokens to evade detection and maintain long-term access

How the Technique Works

Adversaries register or compromise OAuth applications to obtain authorization tokens that grant access to protected resources. By abusing OAuth consent flows or exploiting misconfigurations, attackers can impersonate users or services, enabling them to interact with APIs or cloud services without direct credential theft. This approach allows attackers to operate under the guise of legitimate applications.

Common Methods & Variations

  • Registering malicious OAuth applications to request excessive permissions
  • Compromising legitimate OAuth apps or abusing third-party integrations
  • Targeting cloud identity providers, enterprise identity platforms, or on-premises OAuth implementations
  • Using living-off-the-land techniques by leveraging existing OAuth frameworks and APIs rather than deploying custom tooling

Indicators of Compromise (IOCs)

  • Unusual OAuth application registrations or permission requests
  • Authorization tokens issued outside normal user activity patterns
  • Logs showing anomalous API calls or token usage from suspicious applications
  • Identity provider alerts for consent grants or token issuance anomalies

Detection Strategies

  • Monitoring identity provider logs and OAuth application registration events
  • Behavioral analysis of token usage patterns and API access frequency
  • Correlation of OAuth consent events with endpoint and network activity
  • Signature-based detection of known malicious OAuth application identifiers or scopes

Mitigation & Prevention

  • Enforce least privilege on OAuth application permissions and scopes
  • Implement strict application registration policies and approval workflows
  • Use conditional access policies and multi-factor authentication for consent grants
  • Regularly audit OAuth applications and revoke unused or suspicious authorizations

Response Considerations

  • Immediately revoke compromised OAuth tokens and disable malicious applications
  • Investigate the scope of access granted through abused OAuth applications
  • Review and tighten OAuth consent policies and application permissions
  • Enhance monitoring and alerting for future OAuth-related anomalies

Related Techniques

  • Credential Access via Phishing or Password Spraying leading to OAuth abuse
  • Token Impersonation or Forgery
  • Use of Valid Accounts for lateral movement or persistence

Mapping & References

  • MITRE ATT&CK Tactic: Initial Access, Persistence, Privilege Escalation, Defense Evasion
  • MITRE ATT&CK Technique: OAuth Application Abuse (T1587.001)
  • Public advisories on OAuth security best practices and incident reports from cloud providers
Tags: Access Tokens Application Abuse Cloud Security Defense Evasion Identity Security Initial Access OAuth persistence privilege escalation Threat Detection