Bug-Bounty

Mastering Remote Code Execution A Comprehensive Guide Introduction: Welcome to our blog post on remote code execution (RCE), a concept that plays a crucial role in the world of software development, cybersecurity, and system administration. Remote code execution refers to the ability to run arbitrary code on a remote machine, often with malicious intent. However, it's also an essential tool for legitimate purposes like debugging, testing, and remote administration. In this guide, we will delve into the intricacies of RCE, covering its definition, risks, prevention, and best practices. Let's get started! Understanding Remote Code Execution: Definition and purpose of RCE. Different types of RCE vulnerabilities. Real-world examples of RCE exploits. The Risks of Remote Code Execution: Impact of RCE attacks on system security. Consequences of successful RCE exploits. Notable historical RCE incidents. Common RC E Vulnerabilities: Injection vulnerabilities (e.g., SQL injection, OS co...

 S ecurity is a really important thing but almost we don’t care when building applications. There are a lot of essential security practices, But in this story, I am going to talk about   HTTP Security Headers. In  HTTP requests , Headers hold the metadata about the request/response. Apart from that, Some  HTTP Headers  are used to enforce some security mechanisms. Okay, Let’s jump into the topic… HTTP Strict Transport Security (HSTS) Most websites use  HTTPS  nowadays. Th a t’s really good. But some sites don’t force users to communicate via  HTTPS . Instead, they work on both  HTTP  and  HTTPS . This is really bad. Because Still, they are giving an option to communicate non-securely. HSTS header  helps us to force users to access the site via  HTTPS  only. So basically, When the browser finds this header, It will change the connection to  HTTPS  even if the user tries to access it via  HTTP . Strict-Tr...

  Misconfiguration in Change-password Functionality Leads to Account Takeover Hello everyone , Sasikaran (0xwhitedevil) and this is our first Write-Up ever. This Write-Up describes How we could Takeover any account on a site using some misconfigurations in Change-Password Functionality. We were testing a private program so let’s call it  site.com ,  so let’s start our Journey. While going throw the sandbox environment that is for testing porous ( sandbox.site.com ) we notice a change password function. So we opened the Burb-Suite and intercept the request looking for any issue and we catch this request and start analyzing it So as you   can see we found this Header (X_auth_credentials) that have the same value of the parameter (current Password) in the request body which insure that, If you want to change your current password you must first enter your current password then enter the new password. So we start to ask some questions, What about this header? Does the S...