AEM - How can we prevent blind XPath injection in an AEM Page?? | Community
Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
arunpatidar
arunpatidarAccepted solution
New Participant
Mar 27, 2023 4:03 PM UTC

3 replies

DPrakashRaj
New Participant
Apr 1, 2023 7:36 AM UTC

If it’s a publisher you can bock all the suffix from dispatcher by adding rule in filter section


# Block use of all suffixes on any resource in /content
/0160 { /type "deny" /url "/content*" /suffix "*" }

# Suffix patterns which are needed on the server side can be added in an allow list manner
/0161 { /type "allow" /url "/content/we-retail/us/en/equipment/*" /suffix "/content/we-retail/*" /method "GET" }

 Rule 0160 is for blocking the suffix request from by passing the dispatcher and hitting your aem publisher 

Translate
arunpatidar
arunpatidarAccepted solution
New Participant
Mar 27, 2023 4:03 PM UTC
maryani
maryaniAuthor
Level 2
Mar 27, 2023 4:34 PM UTC

Thank you for the reply

Translate