CVE-2017-5528 [High] | CSRF in Jasperreports Server

Multiple JasperReports Server components contain vulnerabilities which may allow authorized users to perform cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks. The impact of this vulnerability includes the theoretical disclosure of sensitive information. Affects TIBCO JasperReports Server (versions 6.1.1 and below, 6.2.0, 6.2.1, and 6.3.0), TIBCO JasperReports Server Community Edition (versions 6.3.0 and below), TIBCO JasperReports Server for ActiveMatrix BPM (versions 6.2.0 and below), TIBCO Jaspersoft for AWS with Multi-Tenancy (versions 6.2.0 and below), and TIBCO Jaspersoft Reporting and Analytics for AWS (versions 6.2.0 and below).

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.12%	0.57%	+0.45%
2	2023-03-07	0.89%	0.12%	-0.77%
3	2022-02-04	—	0.89%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.12%

0.57%

+0.45%

2023-03-07

0.89%

0.12%

-0.77%

2022-02-04

—

0.89%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]
5.7	3.0	MEDIUM	`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.1	3.6	[email protected]
6.8	2.0	MEDIUM	`AV:N/AC:M/Au:N/C:P/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:M) Exploitation needs some favorable conditions, but not exceptional ones. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	8.6	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

5.7

3.0

MEDIUM

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

2.1

3.6

[email protected]

6.8

2.0

MEDIUM

AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:M): Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

8.6

6.4

[email protected]

OS Trackers for CVE-2017-5528

vendor	priority	summary	link
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2017-5528
`ubuntu`	medium	CVE-2017-5528 medium priority: Ubuntu including 1 source packages (jasperreports), 14 status rows across 14 suites (bionic, focal, groovy, hirsute, impish, jammy, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 11, needed 1, not-affected 1, released 1.	https://ubuntu.com/security/CVE-2017-5528

Affected software / configurations for CVE-2017-5528

Vendor	Product	Version	Raw CPE
tibco	jasperreports_server	<= 6.1.1	cpe:2.3:a:tibco:jasperreports_server::::::::
tibco	jasperreports_server	6.2.0	cpe:2.3:a:tibco:jasperreports_server:6.2.0::::-:-::*
tibco	jasperreports_server	6.2.1	cpe:2.3:a:tibco:jasperreports_server:6.2.1::::-:-::*
tibco	jasperreports_server	6.3.0	cpe:2.3:a:tibco:jasperreports_server:6.3.0::::-:-::*
tibco	jasperreports_server	<= 6.3.0	cpe:2.3:a:tibco:jasperreports_server:::::community:::*
tibco	jasperreports_server	<= 6.2.0	cpe:2.3:a:tibco:jasperreports_server::::::activematrix_bpm::*
tibco	jaspersoft	<= 6.2.0	cpe:2.3:a:tibco:jaspersoft::::::aws_with_multi-tenancy::*
tibco	jaspersoft_reporting_and_analytics	<= 6.2.0	cpe:2.3:a:tibco:jaspersoft_reporting_and_analytics::::::aws::*

References for CVE-2017-5528

URL	Tags
https://www.tibco.com/support/advisories/2017/06/tibco-security-advisory-june-28-2017-tibco-jasperreports-server-2017	Vendor Advisory

URL

CVE-2017-5528 | TIBCO JasperReports Server cross-site vulnerabilities

Exploit prediction scoring system (EPSS) score for CVE-2017-5528

Common vulnerability scoring system (CVSS) metrics for CVE-2017-5528

Weakness enumeration for CVE-2017-5528

OS Trackers for CVE-2017-5528

Affected software / configurations for CVE-2017-5528

References for CVE-2017-5528