Web applications attacks/Client side verifications

From aldeid
Jump to navigation Jump to search

Description

If data sent by the browser are not checked on server-side, it is possible to change values and pass non-standard/non-expected data. In addition, always control authorizations in each page on server-side. If they are only controlled on client-side, a hacker could easily escalate his/her privileges and access non-authorized content.

Examples

Protection

  • You can check data on client side to avoid a roundtrip to the server and hence save bandwidth but these controls have to be also done on server-side.
  • Always check that data match a specific mask (if you are expecting a number, check that nothing but [0-9] is sent)

Tools

Comments

Talk:Web applications attacks/Client side verifications