adobe / adobe/aem-project-archetype
Default Filter rules on AEM Cloud opens way too much
- Dominant language
- JavaScript
- Stars
- 596
- Forks
- 431
- Avg merge
- 10d 6h
- Merged PRs (30d)
- 1
Description
https://github.com/adobe/aem-project-archetype/blob/ea27d77022fb19250492ea04c3ed971ac60adb4e/src/main/archetype/dispatcher.cloud/src/conf.dispatcher.d/filters/default_filters.any#L25
A servlet may be open on publish and should not.
Example: /bin/some-servlet.json.servlet.json/something.js may respond if /bin wasn't blocked afterwards.
Possible solution:
`/0011 { /type "allow" /method "GET" /extension '(css|eot|gif|ico|jpeg|jpg|js|gif|png|svg|swf|ttf|woff|woff2)' /suffix "" /method '(GET|HEAD)' }`
block at least suffixes.
Please doublecheck why this rule is even required, it is NOT present in AMS
Contributor guide
Research direction
Start with src/main/archetype/dispatcher.cloud/src/conf.dispatcher.d/filters/default_filters.any at line 25 and compare the default filter rule with the reported servlet URL and the AMS behavior mentioned in the issue. Confirm which suffixes or paths are exposed, then verify that the resulting filter rules no longer allow the example request while still permitting the listed static extensions.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100