XSS in Apache Axis2/Java Administration Console
A cross-site scripting (XSS) vulnerability exists in the administration console of Apache Axis2/Java versions 1.4.1, 1.5.1, and possibly other versions. The vulnerability is present in the axis2-admin/axis2-admin/engagingglobally endpoint, where the 'modules' parameter is not properly sanitized, allowing remote attackers to inject arbitrary web script or HTML. This issue also affects products embedding Axis2/Java, such as SAP Business Objects 12 and 3com IMC.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows remote attackers to execute arbitrary JavaScript or HTML in the context of the administration console user's browser session. This can lead to session hijacking, credential theft, or other attacks leveraging the trust relationship between the user and the application.
If you can’t patch tonight, do this now.
Restrict access to the administration console to trusted users and networks. Employ web application firewalls (WAFs) to filter malicious input. Disable or remove the vulnerable endpoint if not required.
Patch, then assume compromise.
Upgrade to a patched version of Apache Axis2/Java where input validation and output encoding are properly implemented for the 'modules' parameter in the administration console. If a patch is not available, apply custom input validation or output encoding to mitigate the vulnerability.
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.