1407
lookup that record for presentation to the user. It is likely that an attacker would have to be an
authenticated user in the system. However, the authorization process would not properly check the
data access operation to ensure that the authenticated user performing the operation has sufficient
entitlements to perform the requested data access, hence bypassing any other authorization
checks present in the system.
For example, attackers can look at places where user specific data is retrieved (e.g. search
screens) and determine whether the key for the item being looked up is controllable externally. The
key may be a hidden field in the HTML form field, might be passed as a URL parameter or as an
unencrypted cookie variable, then in each of these cases it will be possible to tamper with the key
value.
One manifestation of this weakness is when a system uses sequential or otherwise easilyguessable
session IDs that would allow one user to easily switch to another user's session and
read/modify their data.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 863 Incorrect Authorization 1787
ParentOf 566 Authorization Bypass Through User-Controlled SQL Primary
Key