[
https://issues.apache.org/jira/browse/SLING-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17286989#comment-17286989
]
Bertrand Delacretaz commented on SLING-10147:
---------------------------------------------
bq. Such an approach requires setting additional ACLs.
Granted, but if we define a {{/system/sling/permissions/webconsole/view}}
resource I think that could be used for other webconsole-related hardening
which is probably useful? I don't have concrete examples right now but I
suppose they would come up if we take a closer look.
And the resource-checking thing is about 4 lines of code compared to more than
100 at https://github.com/apache/sling-org-apache-sling-scripting-core/pull/5
Anyway, feel free to consider my suggestion as just that - if the new code has
strong tests I'm not opposed to merging it. But I'm doubtful about that,
searching for {{/test}} in that PR returns nothing ;-)
> scripting variables implementation details are exposed to not authorized users
> ------------------------------------------------------------------------------
>
> Key: SLING-10147
> URL: https://issues.apache.org/jira/browse/SLING-10147
> Project: Sling
> Issue Type: Bug
> Reporter: Eric Norman
> Priority: Major
> Fix For: Scripting Core 2.3.6
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> The ".SLING_availablebindings.json" selector is registered at
> /apps/sling/servlet/default and the usage on all resources is not protected
> by any security checks. The information returned contains implementation
> details that a regular user should not need to know and could be considered
> an "information disclosure" vulnerability.
> Since this selector appears to only be used by the "Scripting Variables"
> webconsole plugin, I would expect that it should require the same security
> checking that would be needed to access the webconsole.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
