Bug 1510332 – CVE-2017-14941 jasperreports: Cleartext storage of passwords

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1510332 - (CVE-2017-14941) CVE-2017-14941 jasperreports: Cleartext storage of passwords

Summary:	CVE-2017-14941 jasperreports: Cleartext storage of passwords

Status:	CLOSED NOTABUG

Aliases:	CVE-2017-14941

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20170930,repor...
Keywords:	Security

Depends On:
Blocks:	1510334
	Show dependency tree / graph

Reported:	2017-11-07 04:11 EST by Andrej Nemec
Modified:	2018-02-12 04:00 EST (History)
CC List:	16 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-11-07 12:40:53 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrej Nemec 2017-11-07 04:11:20 EST

Jaspersoft JasperReports 4.7 suffers from a saved credential disclosure vulnerability, which allows a remote authenticated user to retrieve stored Data Source passwords by accessing flow.html and reading the HTML source code of the page reached in an Edit action for a Data Source connector.

References:

https://github.com/binary1985/VulnerabilityDisclosure/blob/master/JasperSoft%20JasperReports%20-%204.7%20-%20CVE-2017-14941

Comment 1 Kurt Seifried 2017-11-07 12:40:53 EST

Statement:

Red Hat Product Security is not aware of any supported product that ships the affected component.

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