Bug 794399 (JBEPP-1443) - Able to name portlet with non-valid display name
Summary: Able to name portlet with non-valid display name
Keywords:
Status: VERIFIED
Alias: JBEPP-1443
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: 5.2.0.GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 5.2.x
Assignee: mark yarborough
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-07 21:46 UTC by Viliam Rockai
Modified: 2018-03-31 21:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
CAUSE: Entered text becomes part of portal page HTML as-is, including special characters like angle brackets CONSEQUENCE: Entered text can break a portal page FIX: Prevent entry of angle brackets using NoHTMLTagValidator RESULT: Text that could break a portal page can't be entered any more.
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-1443 0 Minor Closed Able to name portlet with non-valid display name 2016-10-14 02:10:49 UTC

Description Viliam Rockai 2011-12-07 21:46:24 UTC
project_key: JBEPP

go to application registry
in the Web category, click (+) to add new portlet
choose any portlet and to display name put <script>alert('a');</script> and save
for any page, click page edit and add <script>alert('a');</script> portlet to page
when you go to edit mode and change something for the portlet, you cannot save, because portlet has non-valid name and has to be renamed

Comment 1 Thomas Heute 2012-01-13 15:10:11 UTC
Labels: Added: EPP_5_2_1_Candidate


Comment 2 Thomas Heute 2012-02-16 09:52:25 UTC
Labels: Removed: EPP_5_2_1_Candidate 


Comment 3 Marko Strukelj 2012-03-06 10:57:06 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
CAUSE: Entered text becomes part of portal page HTML as-is, including special characters like angle brackets
CONSEQUENCE: Entered text can break a portal page
FIX: Prevent entry of angle brackets using NoHTMLTagValidator
RESULT: Text that could break a portal page can't be entered any more.


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