Wednesday, April 2, 2025
HomeBug BountyOpenAI Launched Bug Bounty Program - Rewards up to $20,000

OpenAI Launched Bug Bounty Program – Rewards up to $20,000

Published on

SIEM as a Service

Follow Us on Google News

It’s been almost half a year since the revolutionary ChatGPT was released. Amazingly, it reached 100 million users in just two months.

ChatGPT has an unimaginable potential to answer things that need a lot of research. Due to its increasingly demanding usage, securing it from threat actors is also essential. 

The Microsoft-backed platform has launched its Bug Bounty Program on BugCrowd. Many Security researchers have already found some vulnerabilities on ChatGPT, and we’re posting them now and then.

However, it is now an excellent opportunity for security professionals to report their bugs and get rewarded for their work.

Their rewards are below as per their Bug bounty program and the VRT (Vulnerability Rating Taxonomy) of Bugcrowd.

  • P4 – $200 – $500
  • P3 – $500 – $1000
  • P2 – $1000 – $2000
  • P1 – $2000 – $6500

The program also mentioned that the reward can go up to a maximum of $20,000, making it a huge reward for critical bugs. So far, 14 Vulnerabilities have been reported on the program.

Scope of the Program

The following applications are in scope.

  • ChatGPT, ChatGPT Plus, Logins, Subscriptions, OpenAI-created Plugins created by users, and all other functionalities.

Bugs that can be reported include,

  • XSS or Stored XSS
  • CSRF
  • SQLi
  • Authentication and Authorization Issues
  • Data Exposure
  • Payment based bugs
  • Cloudflare Bypass to send traffic to unprotected endpoints
  • Running queries on private models that are not available to the Public
  • Browsing or Code Interpreter Plugins created by OpenAI
  • SSRF
  • OAuth Flaws
  • Credential Security and making plugin calls to unrelated domains

Since OpenAI has access to the entire internet, issues related to Google Workspace, Asana, Trella, Jira, Monday.com, Notion, Hubspot, and many more related issues related to OpenAI can also be reported.

However, there are restrictions to perform additional security testing on these companies.

Subdomains of openai are also included in the scope of the program. The subdomains of OpenAI can be found at 

  • *.openai.com

Out-of-Scope Vulnerabilities

Though most bugs are eligible for reporting, some of the bugs listed below are out of the program’s scope.

  • Issues based on the Model
  • Brute Forcing API
  • Fuzzing, password spraying unauthorized attacks
  • Stolen or Leaked Credentials stemming
  • Clickjacking
  • SSL/TLS Cipher security issues with PoC
  • Server error messages without exploit proof
  • Old/EoL browser/ plugins related issues and much more

For more information, refer to the Out-of-Scope topic on BugCrowd.

Struggling to Apply The Security Patch in Your System? – 

Related Read:

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

Google Introduces End-to-End Encryption for Gmail Business Users

Google has unveiled end-to-end encryption (E2EE) capabilities for Gmail enterprise users, simplifying encrypted email...

New Outlaw Linux Malware Using SSH brute-forcing To Maintain Botnet Activities for long Time

A persistent Linux malware known as "Outlaw" has been identified leveraging unsophisticated yet effective...

Hackers Exploit JavaScript & CSS Tricks to Steal Browsing History

The web browsing history feature, designed to enhance user convenience by styling visited links...

Python Introduces New Standard Lock File Format for Enhanced Security

The Python Software Foundation (PSF) has officially announced the adoption of a new standardized...

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

Google Introduces End-to-End Encryption for Gmail Business Users

Google has unveiled end-to-end encryption (E2EE) capabilities for Gmail enterprise users, simplifying encrypted email...

New Outlaw Linux Malware Using SSH brute-forcing To Maintain Botnet Activities for long Time

A persistent Linux malware known as "Outlaw" has been identified leveraging unsophisticated yet effective...

Hackers Exploit JavaScript & CSS Tricks to Steal Browsing History

The web browsing history feature, designed to enhance user convenience by styling visited links...