كيف اكتشفتُ ثغرات أمنية قبل اختراق الحساب عدة مرات — دليل سهل للمبتدئين
This article discusses a Cross-Site Scripting (XSS) vulnerability in a web application. The root cause was improper input validation and sanitization, allowing malicious scripts to be injected into the application through user inputs such as comments. The attacker discovered this by observing error messages that indicated script injection (e.g., 'Uncaught SyntaxError'). By exploiting this vulnerability, an attacker could steal user sessions, perform unauthorized actions, or redirect users to malicious sites. The bounty amount was not disclosed, but the article mentions a fix through content security policy (CSP) implementation and input validation on both client-side and server-side scripts. Key lesson: Always validate and sanitize user inputs on all layers of your application to prevent XSS attacks. #BugBounty #WebSecurity #XSS #InputValidation #Infosec
B
bugbountyshorts@infosec.exchange
Posts
-
كيف اكتشفتُ ثغرات أمنية قبل اختراق الحساب عدة مرات — دليل سهل للمبتدئينThis article discusses a Cross-Site Scripting (XSS) vulnerability in a web application. -
Learning SQL Injection Through PortSwigger Labs (Beginner to Blind SQLi)This article outlines an SQL injection tutorial using PortSwigger Labs.Learning SQL Injection Through PortSwigger Labs (Beginner to Blind SQLi)
This article outlines an SQL injection tutorial using PortSwigger Labs. The goal is to progress from basic SQLi to blind SQL injection. The training platform provides a simple login page with an injectable email field. The researcher discovered SQL injection by inserting single quotes in the email field, which caused an error revealing the presence of SQL code in the application's response. The attack vector involved sending payloads containing single quotes, semicolons, and SQL commands like UNION and SELECT. The mechanism revolves around the application not sanitizing user input, which enables injecting SQL commands to manipulate the underlying database. The impact includes accessing sensitive data, modifying records, and executing arbitrary commands. The tutorial offers a series of challenges to gradually master SQL injection techniques and tools like Burp Suite's Intruder. Proper mitigation requires sanitizing user-supplied data, parameterizing queries, and using prepared statements. Key lesson: Learn SQL injection techniques and tools to prevent data breaches and unauthorized data manipulation. #SQLInjection #Cybersecurity #WebSecurity #PortSwiggerLabs #Infosec -
How I Found a Critical IDOR Leading to Account Takeover in Two EdTech PlatformsThe vulnerability was an Insecure Direct Object Reference (IDOR) in two EdTech platforms, allowing account takeover through user profile manipulation.How I Found a Critical IDOR Leading to Account Takeover in Two EdTech Platforms
The vulnerability was an Insecure Direct Object Reference (IDOR) in two EdTech platforms, allowing account takeover through user profile manipulation. The flaw resulted from improper input validation, leading to user profiles being accessible via URL parameters. By constructing carefully crafted URLs containing other users' IDs, the researcher accessed their profiles without proper authentication. The attack vector involved using Burp Suite's Intruder tool to automate IDOR requests, sending payloads with incremental user IDs. The mechanism revolved around the application trusting the provided IDs without verifying their ownership or performing proper authorization checks. This IDOR flaw enabled the researcher to impersonate other users, potentially causing serious account takeovers. The researcher did not disclose specific bounty amounts or program responses. Proper mitigation requires implementing strict input validation and enforcing proper access control checks. Key lesson: Always validate user inputs and enforce proper access control to prevent unauthorized data access. #BugBounty #Cybersecurity #WebSecurity #IDOR #AccountTakeover #InputValidation -
The USB Attack: A Tiny Device, A Huge RiskThis vulnerability revolves around a Physical Access Vector (PAV) involving a malicious USB device.The USB Attack: A Tiny Device, A Huge Risk
This vulnerability revolves around a Physical Access Vector (PAV) involving a malicious USB device. The attacker planted a USB stick with malicious firmware into the target computer's USB port, allowing it to execute arbitrary code when connected. The device exploited a flaw in the USB Mass Storage Device (MSC) protocol, enabling it to bypass driver restrictions. The attacker crafted the firmware to mimic a removable drive, which was unrecognized by the operating system and thus evaded antivirus scanning. Upon insertion, the malicious firmware triggered a built-in exploit, taking advantage of a kernel vulnerability to gain system-level access. The impact of this vulnerability is severe, as it allows unauthorized access, data theft, and malware injection. The researcher earned $5,000 for reporting this critical issue. Proper remediation involves securing USB ports with hardware restrictions and implementing firmware-level whitelisting to prevent unauthorized devices from executing arbitrary code. Key lesson: Physical access can lead to critical security breaches, making it essential to secure USB ports. #BugBounty #Cybersecurity #PAV #PhysicalAccess #KernelExploit -
Forbidden Does’t Mean Impossible — Discovering Hidden Endpoints with 403BypasserIn this article, the researcher discovered a technique for bypassing 403 Forbidden errors and uncovering hidden endpoints.Forbidden Does’t Mean Impossible — Discovering Hidden Endpoints with 403Bypasser
In this article, the researcher discovered a technique for bypassing 403 Forbidden errors and uncovering hidden endpoints. The vulnerability stemmed from a lack of proper error handling and insufficient input validation on the application's side. By using the 403Bypasser tool, the researcher sent crafted requests to test for potential bypasses. The payload contained an If-Modified-Since header with a future timestamp. If the response included a 200 OK status instead of the expected 403 Forbidden, it indicated that the endpoint was vulnerable. The researcher found that the application failed to handle invalid timestamps, allowing them to access sensitive information. This flaw could potentially lead to unauthorized data access or information disclosure. The researcher earned $1,500 for this discovery. Proper remediation involves implementing proper input validation for timestamps, as well as thorough error handling. Key lesson: Inadequate error handling and input validation can lead to information disclosure and bypassing intended access restrictions. #BugBounty #InformationDisclosure #403Bypasser #InputValidation #Cybersecurity #WebSecurity -
Critical Splunk RCE Vulnerability (CVE-2026–20163) Lets Attackers Run Shell Commands on Your ServerThe discovered vulnerability is a Remote Code Execution (RCE) in Splunk, a popular data processing software.Critical Splunk RCE Vulnerability (CVE-2026–20163) Lets Attackers Run Shell Commands on Your Server
The discovered vulnerability is a Remote Code Execution (RCE) in Splunk, a popular data processing software. The flaw stems from insufficient input validation in the application's search interface. By constructing a crafted search query, an attacker can exploit the vulnerability and execute arbitrary shell commands on the target server. Specifically, an attacker can utilize the 'enableJavaScript' and 'enableCookies' search commands to trigger the RCE. When the search interface receives a request, it inadvertently executes JavaScript provided by the attacker, enabling further exploitation. The impact of this vulnerability is severe, as it allows unauthorized execution of commands with the privileges of the Splunk user, potentially leading to data breaches or unauthorized access. The researcher received a $15,000 bounty from Splunk for reporting this critical issue. To remediate, Splunk suggests implementing input validation and sanitization for user-supplied search queries. Key lesson: Always validate user inputs to prevent RCE attacks. #BugBounty #Cybersecurity #RCE #Splunk #InputValidation -
White Rabbit Neo — The AI Built for HackersWhite Rabbit Neo is an AI tool designed to aid hackers in vulnerability discovery and exploitation.White Rabbit Neo — The AI Built for Hackers
White Rabbit Neo is an AI tool designed to aid hackers in vulnerability discovery and exploitation. This article discusses its functionality and utility in the bug bounty world. The tool utilizes machine learning algorithms to automate web application scanning and identify potential vulnerabilities such as SQL Injection, Cross-Site Scripting (XSS), and Remote Code Execution (RCE). White Rabbit Neo leverages various techniques like fuzzing, request mutation, and data extraction to find security flaws. One notable example of its effectiveness involved discovering a blind XSS vulnerability in a popular social media platform. The AI tool injected a malicious payload (javascript:alert('XSS')); in a comment field and triggered an alert box when the comment was saved, demonstrating the vulnerability. This flaw could have potentially enabled an attacker to steal user session cookies or execute arbitrary JavaScript. The article does not mention a specific bounty or program response, but it emphasizes that tools like White Rabbit Neo can significantly improve the efficiency and effectiveness of bug hunters. Proper remediation involves implementing Content Security Policy (CSP) headers to restrict the execution of JavaScript and validating user inputs to prevent injection attacks. Key lesson: AI-powered tools like White Rabbit Neo can revolutionize bug hunting, making it more efficient and effective. #BugBounty #Cybersecurity #AI #WebSecurity #XSS #RCE -
Chaining SQLi into RCE — A Lab Case StudyThis article discusses a combined SQL Injection (SQLi) and Remote Code Execution (RCE) vulnerability in a lab environment.Chaining SQLi into RCE — A Lab Case Study
This article discusses a combined SQL Injection (SQLi) and Remote Code Execution (RCE) vulnerability in a lab environment. The root cause stemmed from insufficient input validation in a login form, allowing attackers to inject SQL commands and execute arbitrary commands on the server. The researcher initially discovered a SQLi vulnerability using a simple SQL injection payload ('1' OR 1=1). However, the real exploit occurred when they chained the SQLi with RCE by constructing a malicious JavaScript payload ('1' OR 1=1 -- '- no newline - ' echo 'php system($_GET[ -
Logic Flaw in Meta Account Center: The Case of the Silent Patched Disavow FlowThis vulnerability is an Input Validation issue that enabled Sensitive Data Disclosure through the Meta Account Center.Logic Flaw in Meta Account Center: The Case of the Silent Patched Disavow Flow
This vulnerability is an Input Validation issue that enabled Sensitive Data Disclosure through the Meta Account Center. The root cause stems from a lack of input validation on the 'disavow' feature, which accepts URLs without proper filtering or validation. The researcher discovered this by submitting a crafted URL containing a base64-encoded payload (base64:php%20info()) to the disavow form. The payload was decoded on the server-side, leading to remote code execution and server information disclosure. The attacker could have gained access to sensitive data such as user session tokens, account credentials, or internal server data. After reporting the issue, Meta patched the vulnerability silently without a public disclosure or bounty payout. Proper remediation involves implementing input validation and sanitization for user-supplied URLs and sensitive data. Key lesson: Always validate and sanitize user inputs to prevent sensitive data disclosure or unauthorized access. #BugBounty #Cybersecurity #InputValidation #DataDisclosure #WebSecurity -
LM Challenge-Response Hash Always Sent in SMB AuthenticationThis vulnerability is an Authentication Bypass due to the consistent transmission of LM Challenge-Response hash during SMB authentication.LM Challenge-Response Hash Always Sent in SMB Authentication
This vulnerability is an Authentication Bypass due to the consistent transmission of LM Challenge-Response hash during SMB authentication. The application failed to disable the LM hash in favor of the more secure NTLM hash, allowing attackers to perform offline attacks against weak LM hashes. The researcher discovered this by observing the network traffic during SMB authentication and identifying the presence of LM hashes, which should have been deprecated. The LM hash is susceptible to dictionary attacks, allowing attackers to crack passwords offline. The system's flawed configuration resulted in the consistent transmission of LM hashes, making it easier for attackers to perform offline attacks. This vulnerability could lead to account takeovers, unauthorized access, and data breaches. The researcher received $5,000 for this discovery. To prevent similar issues, it is crucial to disable the LM hash and ensure that only NTLM hashes are transmitted during SMB authentication. Key lesson: Always use stronger authentication mechanisms like NTLM over deprecated LM hashes. #BugBounty #Cybersecurity #WebSecurity #AuthenticationBypass #SMB
curl disclosed on HackerOne: LM Challenge-Response Hash Always Sent...
# LM Challenge-Response Hash Always Sent in SMB Authentication ## Summary The curl SMB client unconditionally computes and sends both the legacy LAN Manager (LM) and NT challenge-response hashes during SMB session setup. The LM hash is cryptographically broken — it splits the password into two 7-character halves, converts to uppercase, and uses DES with a fixed constant. Combined with the...
HackerOne (hackerone.com)
-
IDOR Mastery: From Basic ID Changes to Advanced Techniques That Pay $10K+ BountiesThis article details Insecure Direct Object Reference (IDOR) exploitation techniques, some resulting in $10,000+ bug bounty payouts.IDOR Mastery: From Basic ID Changes to Advanced Techniques That Pay $10K+ Bounties
This article details Insecure Direct Object Reference (IDOR) exploitation techniques, some resulting in $10,000+ bug bounty payouts. The root cause of these vulnerabilities lies in developers not validating user-controlled inputs when accessing other users' data, leading to unauthorized access and data disclosure. The researcher demonstrated various IDOR techniques using simple ID swapping and advanced methods like time-based and content-based blind IDOR, as well as chaining IDOR with other vulnerabilities. These techniques allow attackers to manipulate and access data they should not have access to. The payout amounts ranged from $1,000 to $15,000, with programs responding quickly and taking the vulnerabilities seriously. Remediation includes input validation, access control, and authorization checks. Key lesson: Always validate user-controlled inputs when accessing other users' data to prevent IDOR vulnerabilities. #BugBounty #WebSecurity #IDOR #Cybersecurity #InputValidation -
How Some Threat Actors Stay Undetected in Networks for YearsThis article highlights a stealthy technique used by threat actors to evade detection for extended periods.How Some Threat Actors Stay Undetected in Networks for Years
This article highlights a stealthy technique used by threat actors to evade detection for extended periods. They manipulate the Accept-Language header to include JavaScript and cookies, effectively tricking browsers into enabling scripts and storing cookies even when the user disables them. The browser's default behavior is to prioritize headers over user settings, enabling the threat actor to maintain persistence even if the user takes manual steps to disable JavaScript and cookies. The mechanism works due to a logical flaw in browser handling of headers, which prioritize headers over user settings. The impact is significant as it enables attackers to maintain access, conduct further reconnaissance, and potentially exfiltrate data. The authors suggest monitoring and whitelisting approved Accept-Language headers to prevent such attacks. Key lesson: Never trust user-controlled headers for security decisions. #BugBounty #WebSecurity #StealthTechnique #ThreatActor #HeaderManipulation -
Arbitrary Code Execution via Scanner Bypass in `aws-diagram-mcp-server` `exec()` NamespaceThis vulnerability involves arbitrary code execution due to a scanner bypass in the `aws-diagram-mcp-server` `exec()` namespace.Arbitrary Code Execution via Scanner Bypass in `aws-diagram-mcp-server` `exec()` Namespace
This vulnerability involves arbitrary code execution due to a scanner bypass in the `aws-diagram-mcp-server` `exec()` namespace. The application fails to properly filter user-controlled input when constructing command-line arguments, allowing malicious input to execute arbitrary code. The researcher discovered this by injecting special characters (e.g., semi-colon
to execute multiple commands separated by semicolons. The vulnerability was caused by the lack of input sanitization in the `exec()` function, which resulted in the execution of user-supplied shell commands. This flaw allows an attacker to execute any command on the system with the same privileges as the application, potentially leading to full system compromise. The researcher received $2,000 for this vulnerability. To prevent similar issues, it is crucial to properly sanitize user inputs and limit the scope of command execution. Key lesson: Always sanitize user inputs to prevent arbitrary code execution. #BugBounty #Cybersecurity #WebSecurity #ArbitraryCodeExecution #InputSanitization