Bug 1474288 (CVE-2017-5529) - CVE-2017-5529 jasperreports: Information disclosure vulnerability
Summary: CVE-2017-5529 jasperreports: Information disclosure vulnerability
Alias: CVE-2017-5529
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1474290
Blocks: 1474289
TreeView+ depends on / blocked
Reported: 2017-07-24 10:23 UTC by Adam Mariš
Modified: 2021-02-17 01:51 UTC (History)
14 users (show)

Fixed In Version: jasperreports 6.4.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-07-25 01:38:49 UTC

Attachments (Terms of Use)

Description Adam Mariš 2017-07-24 10:23:41 UTC
JasperReports library components contain an information disclosure
vulnerability. This vulnerability includes the theoretical disclosure
of any accessible information from the host file system. Affects TIBCO
JasperReports Library Community Edition (versions 6.4.0 and below),
TIBCO JasperReports Library for ActiveMatrix BPM (versions 6.2.0 and
below), TIBCO JasperReports Professional (versions 6.2.1 and below,
and 6.3.0), TIBCO JasperReports Server (versions 6.1.1 and below,
6.2.0, 6.2.1, 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.3.0 and below), TIBCO Jaspersoft
Reporting and Analytics for AWS (versions 6.3.0 and below), and TIBCO
Jaspersoft Studio for ActiveMatrix BPM (versions 6.2.0 and below).

External References:


Comment 1 Adam Mariš 2017-07-24 10:27:07 UTC
Created jasperreports tracking bugs for this issue:

Affects: fedora-all [bug 1474290]

Comment 2 Kurt Seifried 2017-07-25 01:38:49 UTC

This issue affects the versions of jasperreports as shipped with Red Hat Enterprise Virtualization 3. Red Hat Product Security has rated this issue as having Moderate security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

Note You need to log in before you can comment on or make changes to this bug.