Incorrect Behavior Order Affecting org.apache.wicket:wicket-core package, versions [9.1.0-M1,9.25.0)[10.0.0-M1,10.12.0)

org.apache.wicket:wicket-core is a Java web application framework that takes simplicity, separation of concerns and ease of development to a whole new level. Wicket pages can be mocked up, previewed and later revised using standard WYSIWYG HTML design tools. Dynamic content processing and form handling is all handled in Java code using a first-class component model backed by POJO data beans that can easily be persisted using your favorite technology.

Affected versions of this package are vulnerable to Incorrect Behavior Order via the ResourceIsolationRequestCycleListener in the HTTP protocol component. When an unauthenticated request from another origin targets a protected page, page instantiation can trigger authorization to interrupt the request before the isolation policy checks it; after the victim signs in, continueToOriginalDestination() redirects to the remembered URL, which the listener treats as same-origin. An attacker can therefore make an ordinary Form run onSubmit() with values they chose in the URL’s query string, provided the application registers the listener and resumes intercepted destinations after sign-in.

Notes

• At the resumed-request policy check, if the original cross-origin request carried no origin headers, the default unknownOutcomeAction is ABORT; the attack proceeds in that case only if the application relaxes it with setUnknownOutcomeAction().

Workarounds

• When refusing unauthorized access, throw org.apache.wicket.RestartResponseException instead of org.apache.wicket.RestartResponseAtInterceptPageException; this avoids storing and resuming the requested destination after sign-in, preventing a cross-origin-chosen listener or form submission from running on resume. Visitors will not be returned to the page they originally requested.

• Apache Security Advisory
• GitHub Commit rel/wicket-10.12.0
• GitHub Commit rel/wicket-11.0.0
• GitHub Commit rel/wicket-9.25.0