fix(security): T2.4 hardening: register PSSecurityHeadersFilter in delivery-tier webapps (issue #96) - #97
Merged
Conversation
…livery-tier webapps (issue #96) PR #95 added the reusable PSSecurityHeadersFilter and registered it in the two main Rhythmyx webapps (secure + non-secure). The delivery-tier webapps (comments, feeds, forms, integrations, membership, metadata, polls) did not have any security-header filter, so they were missing: - X-Frame-Options (clickjacking, CWE-1021) - X-Content-Type-Options: nosniff (MIME-sniffing) - Referrer-Policy: strict-origin-when-cross-origin (referrer leakage) - Strict-Transport-Security on HTTPS (downgrade) - X-XSS-Protection: 0 (legacy XSS auditor disabled) This is the same defense-in-depth added to the main Rhythmyx webapps. WebUI/war and system/ear already have the existing PSSecurityHeaderFilter (com.percussion.utils.security.PSSecurityHeaderFilter), which is a richer filter that does X-Frame/XSS/HSTS/CSP/Cache-Control. Adding the new filter there would create duplicate header writes, so they are out of scope for this slice. Verified clean build via ./mvn-env.sh clean install -DskipTests (7 of 7 target modules BUILD SUCCESS; PSSecurityHeadersFilter present in each built WAR's WEB-INF/web.xml). > Co-Authored by Mavis v1.0.0 using minimax-m3 with agent mavis.
natechadwick
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PR #95 added a reusable
PSSecurityHeadersFilter(X-Frame-Options, X-Content-Type-Options, Referrer-Policy, HSTS, X-XSS-Protection: 0) and registered it in the two main Rhythmyx webapps (secure+non-secure). This PR extends the same defense-in-depth to the seven production delivery-tier webapps:comments— user-facing comment threadsfeeds— RSS / Atom feed endpointsforms— form submission webappintegrations— third-party integrations webappmembership— membership profile pagesmetadata— metadata servicepolls— polls serviceEach was previously missing the clickjacking / MIME-sniffing / referrer-leak / HSTS headers. Same
<filter>+<filter-mapping>block is added to eachweb.xml(11 lines per file, 77 lines total). The filter classcom.percussion.security.servlet.PSSecurityHeadersFilteris already on each webapp's classpath via the transitiveperc-shared-app→perc-security-utilsdependency.Out of scope (deliberately)
WebUI/war/WEB-INF/web.xmlandsystem/ear/WEB-INF/web.xml— already have the existingPSSecurityHeaderFilter(com.percussion.utils.security.PSSecurityHeaderFilter), which is a richer filter that also handles CSP and Cache-Control. Adding the new filter there would create duplicate header writes.Verification
./mvn-env.sh clean install -DskipTestsis BUILD SUCCESS for all 7 target modules (comments,feeds,forms,integrations,membership,metadata,polls).unzip -p <war> WEB-INF/web.xml | grep PSSecurityHeadersFilterreturns the expected block for every built WAR.Closes #96.