docs: add summary for OTC CatchUp #267 : added config #323
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
👷 Deploy request for otc-catchup pending review.Visit the deploys page to approve it
|
ankushhKapoor
requested changes
Feb 3, 2026
| ** They explored scenarios where companies might dismiss bug bounty reports, claiming vulnerabilities are outdated or not exploitable, even when they can be demonstrated. | ||
| * Kartik shared experiences with SQL injection attacks and Denial of Service (DoS) scenarios. | ||
| ** He mentioned testing SQL injection vulnerabilities and how injecting payloads could cause sites to freeze or crash. | ||
| ** Kartik discussed an incident where cookie injection led to their EngineX server going down, though it recovered within a couple of minutes. |
Member
There was a problem hiding this comment.
Suggested change
| ** Kartik discussed an incident where cookie injection led to their EngineX server going down, though it recovered within a couple of minutes. | |
| ** He discussed an incident where cookie injection led to their EngineX server going down, though it recovered within a couple of minutes. |
| * Alpesh Bhagwatkar shared his experience with responsible disclosure and company responses to security vulnerabilities. | ||
| ** He discussed an incident involving a large real estate company where he discovered and dumped their entire database. | ||
| ** After reporting the vulnerability, the company responded with legal threats instead of acknowledging the security issue. | ||
| ** Alpesh noted that the vulnerability still exists, highlighting challenges in responsible disclosure when companies respond defensively rather than addressing security concerns. |
Member
There was a problem hiding this comment.
Suggested change
| ** Alpesh noted that the vulnerability still exists, highlighting challenges in responsible disclosure when companies respond defensively rather than addressing security concerns. | |
| ** He noted that the vulnerability still exists, highlighting challenges in responsible disclosure when companies respond defensively rather than addressing security concerns. |
| ** The conversation touched on the importance of proper vulnerability reporting and the need for companies to take security reports seriously. | ||
| * Discussion about an upcoming tech event at Nesco, Mumbai. | ||
| ** The group discussed whether the event was worth attending, with some members noting it was scheduled for a weekend. | ||
| ** Alpesh mentioned sharing an Amazon link in the OTC group related to the event. |
Member
There was a problem hiding this comment.
Please add the link here too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.