appsec.fyi · Sources

masimshahzad.medium.com

7 curated AppSec resources from masimshahzad.medium.com across 8 topics on appsec.fyi.

masimshahzad.medium.com

Resources curated from this publisher and indexed across appsec.fyi topic pages. Last item added: 2026-11-13.

Date Added Resource Excerpt
2026-11-13 2026The Phone Number That Unlocked Any Tinder AccountAuthNBug BountyA security researcher discovered a vulnerability allowing access to any Tinder account using only a phone number. By exploiting the platform's phone number verification process, an attacker could intercept one-time passwords (OTPs) intended for account recovery or creation. This loophole enabled them to gain control of any Tinder profile. The researcher demonstrated the exploit's potential by accessing multiple accounts. The vulnerability has since been fixed by Tinder.
2026-11-13 2026One Missing Anchor, One Flickr XSSBug BountyMobileXSSA Cross-Site Scripting (XSS) vulnerability was discovered in Flickr's mobile application. The flaw stemmed from an unanchored regular expression combined with Cross-Origin Resource Sharing (CORS) misconfigurations. This allowed external HTML content to be executed within the application's origin. The vulnerability was addressed by parsing URLs and comparing their origins to prevent unauthorized execution.
2026-11-11 2026The Referer Header That Redirected OAuth TokensAuthNBug BountyThis article details a security vulnerability where the Referer header was used to redirect OAuth tokens. Attackers could exploit this by crafting a malicious link. When a user clicked this link, the Referer header would contain sensitive OAuth token information, and then redirect the user to a site controlled by the attacker. This allowed attackers to steal these tokens, potentially gaining unauthorized access to user accounts and data.
2026-11-11 2026The CSRF Token Nobody CheckedBug BountyCSRFA critical vulnerability discovered in Messenger.com in 2015 allowed any website to impersonate a logged-in user. This was due to the complete absence of Cross-Site Request Forgery (CSRF) token checks. The bug's root cause was this oversight, and its impact was severe, enabling malicious actors to perform actions on behalf of users without their knowledge or consent. The recommended fix involved implementing a default-deny security policy to ensure CSRF tokens are always validated.
2026-11-08 2026The SSRF That Mailed Out Your OAuth TokenAuthNBug BountySecretsSSRFRon Chan discovered a Server-Side Request Forgery (SSRF) vulnerability in Google Cloud's debugger. This flaw allowed attackers to intercept and exfiltrate users' OAuth tokens by forwarding them to unvalidated URLs. The research details the root cause of the vulnerability, explores potential Cross-Site Request Forgery (CSRF) angles, and outlines the necessary fixes to prevent such token leakage.
2026-10-31 2026Spring4Shell Step by Step: How CVE 2022 22965 Turns Data Binding Into Remote Code Execution in a…Bug BountyRCESpring4Shell (CVE-2022-22965) is a critical vulnerability in the Spring Framework that allows remote code execution (RCE). It exploits how Spring handles data binding, specifically when users can control the `class.module.classLoader` header in HTTP requests. This can lead to attackers injecting malicious code and executing arbitrary commands on vulnerable servers. The vulnerability affects specific configurations of Spring MVC and Spring WebFlux, requiring attackers to also have a way to deploy arbitrary files to the server.
2026-10-31 2026ProxyShell Step by Step: How Three Exchange Flaws Chain Into Remote Code Execution in a LabBug BountyRCEThis content details a step-by-step demonstration of the ProxyShell exploit, which chains three Microsoft Exchange vulnerabilities to achieve remote code execution. The exploit leverages flaws in Exchange's Extended Web Access (EWS), Remote PowerShell (RPS), and the Server Message Block (SMB) protocol. By chaining these vulnerabilities, an attacker can bypass authentication and execute arbitrary code on a vulnerable Exchange server. The process is illustrated within a lab environment, providing a practical understanding of the attack's methodology.