Content deleted Content added
removed Template:Multiple issues & general fixes using AWB (7961) |
|||
Line 1:
A simple example is as follows: Consider a Web application that allows a user to edit pages, and also allows administrators to lock pages to prevent editing. A user requests to edit a page, getting a form by which he can alter its content. Before the user submits the form, an administrator locks the page, which should prevent editing. However, since the user has already begun editing, when he submits the form, his edits are accepted. When the user began editing, his authorization was ''checked'', and he was indeed allowed to edit. However, the authorization was ''used'' later, after he should no longer have been allowed.
Line 78:
== Further reading ==
* Bishop, Matt; and Dilger, Michael; 1996; [http://nob.cs.ucdavis.edu/bishop/papers/1996-compsys/racecond.pdf ''Checking for race conditions in file accesses'']; Computing Systems, Vol. 9, No. 2, pp.
* Tsafrir, Dan; Hertz, Tomer; Wagner, David; and Da Silva, Dilma; 2008; [http://www.cs.berkeley.edu/~daw/papers/tocttou-fast08.pdf ''Portably Solving File TOCTTOU Races with Hardness Amplification''], Proceedings of the 6th USENIX Conference on File and Storage Technologies (FAST '08), San Jose (CA), February 26–29, 2008, pp.
[[Category:Computer security exploits]]
|