Author: mgrigorov
Date: Mon Sep 15 13:14:22 2014
New Revision: 1625026
URL: http://svn.apache.org/r1625026
Log:
add a link to 1.5.12 and fix a typo
Modified:
wicket/common/site/trunk/_posts/2014-09-15-cve-2014-3526.md
Modified: wicket/common/site/trunk/_posts/2014-09-15-cve-2014-3526.md
URL:
http://svn.apache.org/viewvc/wicket/common/site/trunk/_posts/2014-09-15-cve-2014-3526.md?rev=1625026&r1=1625025&r2=1625026&view=diff
==============================================================================
--- wicket/common/site/trunk/_posts/2014-09-15-cve-2014-3526.md (original)
+++ wicket/common/site/trunk/_posts/2014-09-15-cve-2014-3526.md Mon Sep 15
13:14:22 2014
@@ -16,10 +16,10 @@ Description:
When rendering a web page Wicket checks the request url against the one at the
render time. It is possible the application to change the page parameters (this
includes both the query parameters and parameters encoded into the request
path). When the requested url differs with the one at the rendering time Wicket
stores the response (i.e. the page markup) at the server side and issues an
HTTP redirect to the new url. When the second request comes Wicket just flushes
the stored response from the first request into the http output stream. This
way the browser address bar shows the updated page parameters.
When storing the page markup at the server side Wicket uses as an identifier a
pair of the current session id plus the new url. However, Wicket does not check
if user session is temporary (i.e. sessionId is null).
-This could lead to a security issue if two or more users with a temporary
session are redirected to the same url at the same time. Then user1 might see
the markup for user2 which has overrided the markup for user1 while user1 was
following the HTTP redirect. In this way user-sensitive informations can be
seen by other users.
+This could lead to a security issue if two or more users with a temporary
session are redirected to the same url at the same time. Then user1 might see
the markup for user2 which has overridden the markup for user1 while user1 was
following the HTTP redirect. In this way user-sensitive informations can be
seen by other users.
The application developers are recommended to upgrade to:
-- [Apache Wicket 1.5.12]()
+- [Apache Wicket 1.5.12](/2014/09/15/wicket-1.5.12-released.html)
- [Apache Wicket 6.17.0](/2014/08/24/wicket-6.17.0-released.html)
- [Apache Wicket 7.0.0-M3](/2014/08/23/wicket-7.0.0-M3-released.html)
