jbonofre opened a new pull request, #3063:
URL: https://github.com/apache/karaf/pull/3063

   Follow-up to #3057 and #3062.
   
   The shipped command ACLs cover the features that Karaf installs at startup 
(`featuresBoot`). A feature that an admin installs later can add commands with 
no ACL, including commands that run code: for example `groovy:exec` / 
`groovy:exec-file` before #3062. The security model didn't say how we treat 
that case, and its viewer bullet read as if it were a vulnerability.
   
   This PR:
   
   - **Roles and ACLs:** says that the shipped ACLs cover the boot features, 
and that a feature installed later can add commands with no ACL, so the 
operator should check its commands (or set 
`karaf.secured.command.compulsory.roles`) before giving console access to users 
with lower roles.
   - **What we treat as a vulnerability:** limits the viewer case to a Karaf 
with only the features that it installs at startup.
   - **What we treat as hardening:** adds a command with no ACL, added by a 
feature that Karaf doesn't install at startup, that gives a lower role the 
effect of an operation reserved to a higher role (such as running code). We 
still fix these, as regular bugs, like #3062.
   
   JMX isn't affected: `etc/jmx.acl.cfg` already restricts MBeans with no 
specific ACL to `admin`.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to