Bug 910931 – CVE-2013-0283 Katello: Username in Notification page XSS

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 910931 - (CVE-2013-0283) CVE-2013-0283 Katello: Username in Notification page XSS

Summary:	CVE-2013-0283 Katello: Username in Notification page XSS

Status:	CLOSED CURRENTRELEASE

Aliases:	CVE-2013-0283

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=20140711,repor...
Keywords:	Security

Depends On:	995666
Blocks:	910963 1000138
	Show dependency tree / graph

Reported:	2013-02-13 17:00 EST by Kurt Seifried
Modified:	2015-08-21 17:18 EDT (History)
CC List:	10 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-01-17 00:33:10 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 Kurt Seifried 2013-02-13 17:00:27 EST

Suresh Thiru (sthirugn@redhat.com) reports:

Description of problem:
In Notifications page, the Username should escape html characters

Steps to Reproduce:
1. Create a user named <blink>FOOO</blink>
2. Go to Notifications page and notice that FOOO is in blinking mode in the page
  
Actual results:
FOOO is in html blinking mode in the Notifications page

Expected results:
Username should be displayed fully in Notifications page: <blink>FOOO</blink>

Additional info:
This was introduced with https://bugzilla.redhat.com/show_bug.cgi?id=813291

Comment 1 Kurt Seifried 2013-07-26 03:38:39 EDT

The Red Hat Security Response Team has rated this issue as having moderate security impact in CloudForms 1.1. This issue is not currently planned to be addressed in future updates.

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