Home Did you know ? Web Applications Attacks: Insecure Direct Object Reference

Web Applications Attacks: Insecure Direct Object Reference

by Unallocated Author

Insecure Direct Object Reference, more generally known as “IDOR”, is a permission based flaw which enables an attacker or a hacker to access or modify resources that belong to other users of the web application, or rather resources which are not permitted to be controlled by the attacker.

The primary key behind Insecure Direct Object Reference is that a part of a web application attempts to display or modify some resource such as a message, image, or file using a user-supplied (or user-controlled) identifier in the request, but doesn’t check whether the user has sufficient permission to perform the task.

XSS (cross site scripting) and CSRF (cross-site request forgery) vulnerabilities are difficult to discover nowadays because web development frameworks such as Rails or Django have built-in filters for XSS and token mechanisms for CSRF, whereas IDOR is a permission-relevant problem and cannot be fixed automatically or by default as permission use-cases change from the web application to web application. So this type of vulnerability is everywhere, in fact, it is so common that the majority of the publicly-disclosed Facebook security bugs are Insecure Direct Object References.

Preventing insecure direct object references flaws requires selecting an approach for protecting each user accessible object (such as object number, filename): Use per user or session indirect object references. This will prevent hackers from directly targeting unauthorized resources.

You may also like

Latest Hacking News

Privacy Preference Center


The __cfduid cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis.

cookie_notice_accepted and gdpr[allowed_cookies] are used to identify the choices made from the user regarding cookie consent.

For example, if a visitor is in a coffee shop where there may be several infected machines, but the specific visitor's machine is trusted (for example, because they completed a challenge within your Challenge Passage period), the cookie allows Cloudflare to identify that client and not challenge them again. It does not correspond to any user ID in your web application, and does not store any personally identifiable information.

__cfduid, cookie_notice_accepted, gdpr[allowed_cookies]


DoubleClick by Google refers to the DoubleClick Digital Marketing platform which is a separate division within Google. This is Google’s most advanced advertising tools set, which includes five interconnected platform components.

DoubleClick Campaign Manager: the ad-serving platform, called an Ad Server, that delivers ads to your customers and measures all online advertising, even across screens and channels.

DoubleClick Bid Manager – the programmatic bidding platform for bidding on high-quality ad inventory from more than 47 ad marketplaces including Google Display Network.

DoubleClick Ad Exchange: the world’s largest ad marketplace for purchasing display, video, mobile, Search and even Facebook inventory.

DoubleClick Search: is more powerful than AdWords and used for purchasing search ads across Google, Yahoo, and Bing.

DoubleClick Creative Solutions: for designing, delivering and measuring rich media (video) ads, interactive and expandable ads.



The _ga is asssociated with Google Universal Analytics - which is a significant update to Google's more commonly used analytics service. This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports. By default it is set to expire after 2 years, although this is customisable by website owners.

The _gat global object is used to create and retrieve tracker objects, from which all other methods are invoked. Therefore the methods in this list should be run only off a tracker object created using the _gat global variable. All other methods should be called using the _gaq global object for asynchronous tracking.

_gid works as a user navigates between web pages, they can use the gtag.js tagging library to record information about the page the user has seen (for example, the page's URL) in Google Analytics. The gtag.js tagging library uses HTTP Cookies to "remember" the user's previous interactions with the web pages.

_ga, _gat, _gid