Summary of Bug Bounty Basic Part one
You should now have a basic understanding of how the internet works. Specifically, you learned what happens when you enter a website into your browser’s address bar: how the browser translates that to a domain, how the domain is mapped to an IP address, and how an HTTP request is sent to a server Bug Bounty basic Part One.
You also learned how your browser structures requests and renders responses and how HTTP request methods allow clients to communicate with servers. Additionally, you learned that vulnerabilities result from someone performing an unintended action or gaining access to information otherwise not available and that bug bounties are rewards for ethically discovering and reporting vulnerabilities to the owners of websites Bug Bounty basic Part One.
If you’re new hacking, it’ll help to possess a basic understanding of how the web works and what happens under the hood once you enter a URL into a browser’s address bar. Although navigating to an internet site might sound simple, it involves many hidden processes, like preparing an HTTP request, identifying the domain to send the request to, translating the domain to an IP address, sending the request, rendering a response, and so on.
In this chapter, you’ll learn basic concepts and terminology, like vulnerabilities, bug bounties, clients, servers, IP addresses, and HTTP. You’ll get a general understanding of how performing unintended actions and providing unexpected input or access to non-public information may result in vulnerabilities. Then, we’ll see what happens once you enter a URL in your browser’s address bar, including what HTTP requests and responses appear as if and therefore the various HTTP action verbs. We’ll end the chapter with an understanding of what it means to mention HTTP is stateless Bug Bounty basic Part One Bug Bounty basic Part One.
Vulnerabilities and Bug Bounties
A vulnerability may be a weakness in an application that permits a malicious person to perform some unpermitted action or gain access to information they shouldn’t rather be allowed to access.
As you learn and test applications, confine mind that vulnerabilities may result from attackers performing intended and unintended actions. for instance , changing the ID of a record identifier to access information you shouldn’t have access to is an example of an unintended action.
Suppose an internet site allowed you to make a profile together with your name, email, birthday, and address. it might keep your information private and share it only together with your friends. But if the web site allowed anyone to feature you as a lover without your permission, this is able to be a vulnerability. albeit the location kept your information private from non-friends, by allowing anyone to feature you as a lover , anyone could access your information. As you test a site, always consider how someone could abuse existing functionality Bug Bounty basic Part One Bug Bounty basic Part One.
A bug bounty may be a reward an internet site or company gives to anyone who ethically discovers a vulnerability and reports it thereto website or company. Rewards are often monetary and range from tens of dollars to tens of thousands of dollars. Other samples of bounties include cryptocurrencies, air miles, reward points, service credits, and so on.
When a corporation offers bug bounties, it creates a program, a term that we’ll use during this book to denote the principles and framework established by companies for people that want to check the corporate for vulnerabilities. Note that this is often different from companies that operate a vulnerability disclosure program (VDP). Bug bounties offer some monetary reward, whereas a VDP doesn’t offer payment (though a corporation may award swag). A VDP is simply how for ethical hackers to report vulnerabilities to a corporation for that company to repair . Although not all reports included during this book were rewarded, they’re all examples from hackers participating in bug bounty programs Bug Bounty basic Part One.
Client and Server Bug Bounty basic Part One
Your browser relies on the web , which may be a network of computers that send messages to every other. We call these messages packets. Packets include the info you’re sending and knowledge about where that data is coming from and where it’s going. Every computer on the web has an address for sending packets thereto . But some computers only accept certain sorts of packets, et al. only allow packets from a restricted list of other computers. It’s then up to the receiving computer to work out what to try to to with the packets and the way to reply . For the needs of this book, we’ll focus only on the info included within the packets (the HTTP messages), not the packets themselves.
I’ll ask these computers as either clients or servers. the pc initiating requests is usually mentioned because the client no matter whether the request is initiated by a browser, instruction , or so on. Servers ask the websites and web applications receiving the requests. If the concept is applicable to either clients or servers, I ask computers generally Bug Bounty basic Part One.
Because the web can include any number of computers lecture one another , we’d like guidelines for a way computers should communicate over the web . This takes the shape of Request for Comment (RFC) documents, which define standards for a way computers should behave. for instance , the Hypertext Transfer Protocol (HTTP) defines how your internet browser communicates with a foreign server using Internet Protocol (IP). during this scenario, both the client and server must comply with implement an equivalent standards in order that they can understand the packets each is sending and receiving Bug Bounty basic Part One.
What Happens once you Visit an internet site
Because we’ll specialise in HTTP messages during this book, this section provides you with a high-level overview of the method that happens once you enter a URL in your browser’s address bar.
Step 1: Extracting the name
Once you enter http://www.google.com/, your browser determines the name from the URL. a website name identifies which website you’re trying to go to and must adhere to specific rules as defined by RFCs. for instance , a website name can only contain alphanumeric characters and underscores. An exception is internationalized domain names, which are beyond the scope of this book. to find out more, ask RFC 3490, which defines their usage. during this case, the domain is www.google.com. The domain is a method to seek out the server’s address.
Step 2: Resolving an IP Address
After determining the name , your browser uses IP to seem up the IP address related to the domain. This process is mentioned as resolving the IP address, and each domain on the web must resolve to an IP address to figure .
Two types of IP addresses exist: Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). IPv4 addresses are structured as four numbers connected by periods, and each number falls in a range from 0 to 255. IPv6 is the newest version of the Internet Protocol. It was designed to address the problem of available IPv4 addresses running out. IPv6 addresses are made up of eight groups of four hexadecimal digits separated by colons, but methods exist to shorten IPv6 addresses. For example, 184.108.40.206 is an IPv4 address, and 2001:4860:4860::8888 is a shortened IPv6 address.
To look up an IP address using just the domain name, your computer sends a request to Domain Name System (DNS) servers, which consist of specialized servers on the internet that have a registry of all domains and their matching IP addresses. The preceding IPv4 and IPv6 addresses are Google DNS servers Bug Bounty basic Part One.
In this example, the DNS server you connect to would match www.google.com to the IPv4 address 220.127.116.11 and send that back to your computer. To learn more about a site’s IP address, you can use the command dig A site.com from your terminal and replace site.com with the site you’re looking up Bug Bounty basic Part One.
Step 3: Establishing a TCP Connection
Next, the computer attempts to establish a Transmission Control Protocol (TCP) connection with the IP address on port 80 because you visited a site using http://. The details of TCP aren’t important other than to note that it’s another protocol that defines how computers communicate with each other. TCP provides two-way communication so that message recipients can verify the information they receive and nothing is lost in transmission Bug Bounty basic Part One.
The server you’re sending a request to might be running multiple services (think of a service as a computer program), so it uses ports to identify specific processes to receive requests. You can think of ports as a server’s doors to the internet. Without ports, services would have to compete for the information being sent to the same place. This means that we need another standard to define how services cooperate with each other and ensure that the data for one service isn’t stolen by another. For example, port 80 is the standard port for sending and receiving unencrypted HTTP requests. Another common port is 443, which is used for encrypted HTTPS requests. Although port 80 is standard for HTTP and 443 is standard for HTTPS, TCP communication can happen on any port, depending on how an administrator configures an application.
You can establish your own TCP connection to a website on port 80 by opening your terminal and running nc <IP ADDRESS> 80. This line uses the Netcat utility nc command to create a network connection for reading and writing messages Bug Bounty basic Part One.
Step 4: Sending an HTTP Request
Continuing with http://www.google.com/ as an example, if the connection in step 3 is successful, your browser should prepare and send an HTTP request, as shown in Listing 1-1:
➊ GET / HTTP/1.1
➋ Host: www.google.com
➌ Connection: keep-alive
➍ Accept: application/html, */*
➎ User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/72.0.3626.109 Safari/537.36
Listing 1-1: Sending an HTTP request
The browser makes a GET request to the / path ➊, which is the website’s root. A website’s content is organized into paths, just like the folders and files on your computer. As you get deeper into each folder, the path you take is denoted by recording each folder’s name followed by a /. When you visit the first page of a website, you access the root path, which is just a /. The browser also indicates it’s using the HTTP version 1.1 protocol. A GET request just retrieves information. We’ll learn more about it later Bug Bounty basic Part One.
The host header ➋ holds an additional piece of information that is sent as part of the request. HTTP 1.1 needs it to identify where a server at the given IP address should send the request because IP addresses can host multiple domains. A connection header ➌ indicates the request to keep the connection with the server open to avoid the overhead of constantly opening and closing connections Bug Bounty basic Part One.
You can see the expected response format at ➍. In this case, we’re expecting application/html but will accept any format, as indicated by the wildcard (*/*). There are hundreds of possible content types, but for our purposes, you’ll see application/html, application/json, application/octet-stream, and text/plain most often. Finally, the User-Agent ➎ denotes the software responsible for sending the request Bug Bounty basic Part One.
Step 5: Server Response
In response to our request, the server should respond with something that looks like Listing 1-2:
➊ HTTP/1.1 200 OK
➋ Content-Type: text/html
Listing 1-2: Server response
follow Bug Bounty basic Part One Bug Bounty basic Part One
Here, we’ve received an HTTP response with the status code 200 ➊ adhering to HTTP/1.1. The status code is important because it indicates how the server is responding. Also defined by RFC, these codes typically have three-digit numbers that begin with 2, 3, 4, or 5. Although there is no strict requirement for servers to use specific codes, 2xx codes typically indicate a request was successful Bug Bounty basic Part One.
Because there is no strict enforcement of how a server implements its use of HTTP codes, you might see some applications respond with a 200 even though the HTTP message body explains there was an application error. An HTTP message body is the text associated with a request or response ➌. In this case, we’ve removed the content and replaced it with –snip– because of how big the response body from Google is. This text in a response is usually the HTML for a web page but could be JSON for an application programming interface, file contents for a file download, and so on. Bug Bounty basic Part One
The Content-Type header ➋ informs the browsers of the body’s media type. The media type determines how a browser will render body contents. But browsers don’t always use the value returned from an application; instead, browsers perform MIME sniffing, reading the first bit of the body contents to determine the media type for themselves. Applications can disable this browser behavior by including the header X-Content-Type-Options: nosniff, which is not included in the preceding example.
Other response codes starting with 3 indicate a redirection, which instructs your browser to make an additional request. For example, if Google theoretically needed to permanently redirect you from one URL to another, it could use a 301 response. In contrast, a 302 is a temporary redirect.
When a 3xx response is received, your browser should make a new HTTP request to the URL defined in a Location header, as follows:
HTTP/1.1 301 Found
Responses starting with a 4 typically indicate a user error, such as response 403 when a request doesn’t include proper identification to authorize access to content despite providing a valid HTTP request. Responses starting with a 5 identify some type of server error, such as 503, which indicates a server is unavailable to handle the sent request.
Step 6: Rendering the Response Bug Bounty basic Part One
Because the server sent a 200 response with the content type text/html, our browser will begin rendering the contents it received. The response’s body tells the browser what should be presented to the user.
The agreement between client and server on how to handle HTTP messages includes defining request methods. A request method indicates the purpose of the client’s request and what the client expects as a successful result. For example, in Listing 1-1, we sent a GET request to http://www.google.com/ implying we expect only the contents of http://www.google.com/ to be returned and no other actions to be performed. Because the internet is designed as an interface between remote computers, request methods were developed and implemented to distinguish between the actions being invoked Bug Bounty basic Part One.
The next section provides a brief overview of request methods you’ll find. Bug Bounty basic Part One
The GET method retrieves whatever information is identified by the request Uniform Resource Identifier (URI). The term URI is commonly used synonymously with Uniform Resource Locator (URL). Technically, a URL is a type of URI that defines a resource and includes a way to locate that resource by way of its network location. For example, http://www.google.com/<example>/file.txt and /<example>/file.txt are valid URIs. But only http://www.google.com/<example>/file.txt is a valid URL because it identifies how to locate the resource via the domain http://www.google.com. Despite the nuance, we’ll use URL throughout the book when referencing any resource identifiers Bug Bounty basic Part One.
The HEAD method is identical to the GET method except the server must not return a message body in the response Bug Bounty basic Part One Bug Bounty basic Part One.
The POST method invokes some function on the receiving server, as determined by the server. In other words, typically there will be some type of backend action performed, such as creating a comment, registering a user, deleting an account, and so on. The action performed by the server in response to a POST can vary. Sometimes, the server may take no action at all. For example, a POST request could cause an error to occur while a request is being processed, and a record wouldn’t be saved on the server Bug Bounty basic Part One.
The PUT method invokes some function that refers to an already existing record on the remote website or application. For example, it might be used when updating an account, a blog post, or so on that already exists. Again, the action performed can vary and might result in the server taking no action at all Bug Bounty basic Part One.
The DELETE method requests that the remote server delete a remote resource identified with a URI Bug Bounty basic Part One.
The TRACE method is another uncommon method; it is used to reflect the request message back to the requester. It allows the requester to see what is being received by the server and to use that information for testing and collecting diagnostic information Bug Bounty basic Part One.
The CONNECT method is reserved for use with a proxy, a server that forwards requests to other servers. This method starts two-way communications with a requested resource. For example, the CONNECT method can access websites that use HTTPS via a proxy.
The OPTIONS method requests information from a server about the communication options available. For example, by calling for OPTIONS, you can find out whether the server accepts GET, POST, PUT, DELETE, and OPTIONS calls. This method won’t indicate whether a server accepts HEAD or TRACE calls. Browsers automatically send this type of request for specific content types, such as application/json. This method, referred to as a preflight OPTIONS call, is discussed more in depth in Chapter 4 because it serves as a CSRF vulnerability protection.
HTTP Is Stateless
HTTP requests are stateless, which means that every request sent to a server is treated as a brand-new request. The server knows nothing about its previous communication with your browser when receiving a request. This is problematic for most sites because the sites want to remember who you are. Otherwise, you’d have to reenter your username and password for every HTTP request sent. This also means that all the data required to process an HTTP request must be reloaded with every request a client sends to a server Bug Bounty basic Part One Bug Bounty basic Part One.
To clarify this confusing concept, consider this example: if you and I had a stateless conversation, before every sentence spoken, I’d have to start with “I’m Peter Yaworski; we were just discussing hacking.” You’d then have to reload all the information about what we were discussing about hacking. Think of what Adam Sandler does for Drew Barrymore every morning in 50 First Dates (if you haven’t seen the movie, you should). Bug Bounty basic Part One
if You Like our Article You can check our Youtube Channel Blackhat Pakistan Also checkout our Blackhat Hacking course in urdu/hindi Checkout The Posts Below Comment if you Like Thank You. Bug Bounty basic Part One