Apache Wicket information disclosure vulnerability

2014.02.06
Risk: High
Local: No
Remote: Yes
CWE: CWE-noinfo


CVSS Base Score: 5/10
Impact Subscore: 2.9/10
Exploitability Subscore: 10/10
Exploit range: Remote
Attack complexity: Low
Authentication: No required
Confidentiality impact: Partial
Integrity impact: None
Availability impact: None

Severity: Important Vendor: The Apache Software Foundation Affected versions: Apache Wicket 1.4.22, 1.5.10 and 6.7.0 Description CVE-2013-2055<https://wicket.apache.org/2014/02/06/cve-2013-2055.html> It is possible to make Wicket deliver the HTML templates in their raw/non-processed form. An attacker could see any sensitive information in the part of the HTML template that is usually ignored during rendering. For example if there is sensitive information before or after the Wicket Panel/Border's markup: [something sensitive here 1] <wicket:panel> [real application code] </wicket:panel> [something sensitive here 2] Usually Wicket will render only the [real application code] part but by exploiting this vulnerability an attacker can see also the code with the sensitive information. The application developers are recommended to upgrade to: - Apache Wicket 1.4.23<https://wicket.apache.org/2014/02/06/wicket-1.4.23-released.html> - Apache Wicket 1.5.11<https://wicket.apache.org/2014/02/06/wicket-1.5.11-released.html> - Apache Wicket 6.8.0<https://wicket.apache.org/2013/05/17/wicket-6.8.0-released.html> and/or to remove any sensitive information in the HTML templates. Apache Wicket Team

References:

https://wicket.apache.org/2014/02/06/wicket-1.4.23-released.html
https://wicket.apache.org/2014/02/06/wicket-1.5.11-released.html
https://wicket.apache.org/2013/05/17/wicket-6.8.0-released.html


Vote for this issue:
50%
50%


 

Thanks for you vote!


 

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.


(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2024, cxsecurity.com

 

Back to Top