Bug 794400 (JBEPP-1444) - able to save wsrp producer property with non-valid name
Summary: able to save wsrp producer property with non-valid name
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-1444
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: 5.2.0.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.1.GA
Assignee: claprun@redhat.com
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-07 21:51 UTC by Viliam Rockai
Modified: 2015-09-01 03:31 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-01-05 11:09:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-1444 0 None Closed able to save wsrp producer property with non-valid name 2012-04-10 04:14:07 UTC

Description Viliam Rockai 2011-12-07 21:51:56 UTC
project_key: JBEPP

go to WSRP producer properties page
add new property with name <script>alert('a');</script>, with label whatever and with hint whatever
click save - error message about non-valid name is shown

log-out and log-in, go to WSRP producer properties again
the property was saved, despite non-valid name

Comment 1 Chris Laprun 2011-12-09 15:02:03 UTC
I believe this is an instance of the session eviction issue. Basically, if you log out and log back in with the same user, no data is evicted.
I still agree that this should be handled better.

Comment 2 Chris Laprun 2011-12-13 13:36:38 UTC
Link: Added: This issue depends GTNWSRP-275


Comment 3 Chris Laprun 2011-12-13 14:36:47 UTC
Release Notes Docs Status: Added: Not Yet Documented
Release Notes Text: Added: Values input in the registration properties field in the Producer configuration part of the WSRP administration portlet were not properly validated resulting in errors further down the stack (in particular at the persistence level), inconsistent user interface and possible XSS. Input is now properly validated and errors should now be caught much earlier, thus avoiding invalid values to propagate to lower levels of the WSRP service.


Comment 4 Chris Laprun 2012-01-05 11:09:42 UTC
Fixed with upgrade to a more recent WSRP version.

Comment 5 Jared MORGAN 2012-03-22 03:13:02 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:
Values input in the registration properties field in
the Producer configuration part of the WSRP administration portlet were not properly validated. This resulted in errors further down the stack (in particular at the persistence level), an inconsistent user interface, and possible XSS vulnerabilities. Input is now properly validated and errors should now be caught much earlier, rherefore avoiding invalid values to propagate to lower levels of the WSRP service.


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