CVE-2017-5532 TIBCO JasperReports persistent cross site scripting
Authorized users can perform persistent cross-site scripting attacks in the report renderer component of TIBCO JasperReports products.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2017-5532?
CVE-2017-5532 is a medium-severity cross-site scripting vulnerability in TIBCO JasperReports Library, published on 15 Nov 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
A vulnerability in the report renderer component of TIBCO JasperReports Server, TIBCO JasperReports Server Community Edition, TIBCO JasperReports Server for ActiveMatrix BPM, TIBCO JasperReports Library, TIBCO JasperReports Library for ActiveMatrix BPM, TIBCO Jaspersoft for AWS with Multi-Tenancy, TIBCO Jaspersoft Reporting and Analytics for AWS, TIBCO Jaspersoft Studio, and TIBCO Jaspersoft Studio for ActiveMatrix BPM may allow a subset of authorized users to perform persistent cross-site scripting (XSS) attacks. Affected releases are TIBCO JasperReports Server 6.2.3 and below; 6.3.0; 6.3.1; 6.3.2; 6.4.0, TIBCO JasperReports Server Community Edition 6.4.0 and below, TIBCO JasperReports Server for ActiveMatrix BPM 6.4.0 and below, TIBCO JasperReports Library 6.2.3 and below; 6.3.0; 6.3.1; 6.3.2; 6.4.0; 6.4.1, TIBCO JasperReports Library for ActiveMatrix BPM 6.4.1 and below, TIBCO Jaspersoft for AWS with Multi-Tenancy 6.4.0 and below, TIBCO Jaspersoft Reporting and Analytics for AWS 6.4.0 and below, TIBCO Jaspersoft Studio 6.2.3 and below; 6.3.0; 6.3.1; 6.3.2; 6.4.0, and TIBCO Jaspersoft Studio for ActiveMatrix BPM 6.4.0 and below.
Weakness: CWE-79
Which versions are affected by CVE-2017-5532?
It affects 5 products.
Products include Tibco Jasperreports Library, Tibco Jasperreports Server, Tibco Jaspersoft, Tibco Jaspersoft Reporting and Analytics, Tibco Jaspersoft Studio.
How do I fix CVE-2017-5532?
No fix has been published for CVE-2017-5532 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2017-5532 being exploited?
There is no known exploitation of CVE-2017-5532 in the wild and no public exploit code.
Other vulnerabilities in TIBCO JasperReports Library
Sources
Also known as GHSA-cwm8-8754-76qc, UBUNTU-CVE-2017-5532.