Security of hidden ID in views

Question

0.00/5 (No votes)

See more:

for editing a data in views we should specify an "Id" to submit to out controller. but imagine that user manually change "Id" value. for example Id=10 change to Id=15 (by some tools in browser like Inspect). in this case EF update data with Id value 15 and trick our application. what is the best solution to overcome this issue?

please help for this issue and mentioned solution. thanks

What I have tried:

My Solution: in each domain class create a property named "UniqueId" as string type and when we add data to database, this property must be valued with GUID besides "Id" value. now when we send view to user UI we must send both property "Id" & "UniqueId" as hidden, then when client post data to controller for update, our logic section shall check "Id" & "UniqueId" both together and if any nonconformity existed, we can throw exception.

Posted 11-Apr-22 9:42am

mmbguide

Updated 11-Apr-22 16:39pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2022-04-11T16:39:00

Solution 1

The user should never see the ID value, let alone be able to change it. If needed, you can include the ID value in a Hidden element in your page, but never let the user change it.

You don't need the extra id value of a GUID, but using a GUID as the primary key in a table is preferred over using an integer.

Posted 11-Apr-22 16:39pm

Dave Kreskowiak

Comments

Peter_in_2780 12-Apr-22 3:28am

I think the OP's point is that hidden elements can be manipulated using browser dev tools.

Dave Kreskowiak 12-Apr-22 8:00am

Yeah, I wasn't entirely sure what he was talking about, so that's why I suggested using the GUID as the PK.