You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2017/08/31 12:23:01 UTC
[jira] [Assigned] (KARAF-5330) Default access control list for
console allows any user to cat files, and write to files.
[ https://issues.apache.org/jira/browse/KARAF-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-5330:
-------------------------------------------
Assignee: Jean-Baptiste Onofré
> Default access control list for console allows any user to cat files, and write to files.
> -----------------------------------------------------------------------------------------
>
> Key: KARAF-5330
> URL: https://issues.apache.org/jira/browse/KARAF-5330
> Project: Karaf
> Issue Type: Bug
> Reporter: Tom Quarendon
> Assignee: Jean-Baptiste Onofré
> Fix For: 4.2.0, 4.0.10, 4.1.3
>
>
> The shell:cat command has no access control list associated with it in the default configuration.
> The same is true of the "shell:ls" command. There may be other shell: commands too that can provide filesystem access. I don't know whether cd, pwd for example should be secured. "tac" most certainly should.
> This means that any user that can access the ssh console can navigate the filesystem, reading and writing files as they like.
> For example, given the default configuration, if I have a "normal" user and can therefore access the console, I can use shell commands to find our or guess the location of the karaf install (shell:pwd will do that), then cat the contents of the etc/users.properties file and find out all users passwords (in the default configuration the passwords are in plain text). I can also cat the etc/host.key file which would seem undesirable.
> tac clearly would be a very dangerous command to have access to. It seems likely that I could subvert many things by just writing directly to configuration files using tac. I could, for example, change, or at least invalidate the admin password by rewriting the users.properties file.
> All in all this feels like a major issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)