Javamelody blind XSS through X-Forwarded-For header

2013.09.27
Credit: Rafael Luque
Risk: Low
Local: No
Remote: Yes
CWE: CWE-79


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

Javamelody [1] includes a blind XSS vulnerability. An attacker could provide an specially-crafted "X-Forwarded-For" HTTP header while visiting a Java web application monitored with Javamelody that would lead to arbitrary HTML or Javascript execution in the context of the administrator user monitoring the panel of active sessions in the application. The versions affected are the last one 1.46 and all the previous that include the session monitoring panel feature. The issue has been reported to the project [2] but whithout response by now. The proof of concept may use the own Javamelody online demo: 1. Access the demo site [3] using a fake X-Forwarded-For header like the following: <script>alert('xss')</script> 2. Then visit the Javamelody sessions monitoring page at [4] and you should see the Javascript running. Can you allocate a CVE identifier for this? Thank you && Regards, Rafael Luque [1] https://code.google.com/p/javamelody/ [2] https://code.google.com/p/javamelody/issues/detail?id=346 [3] http://demo.javamelody.cloudbees.net/ [4] http://demo.javamelody.cloudbees.net/monitoring?part=sessions

References:

http://demo.javamelody.cloudbees.net/monitoring?part=sessions
https://code.google.com/p/javamelody/issues/detail?id=346


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