Red Hat Bugzilla – Bug 491227
Security Officer: An User token can be used to enroll/format another user token.
Last modified: 2015-01-04 18:37:29 EST
Description of problem:
An user token can be used to enroll/format another user token.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Enroll a security officer token, SOfficer1.
2. Login to Security Officer station with the SOfficer1 token.
3. Enroll a blank token for a user, User1
4. Close the Security officer window. Remove Security officer and user token from the hook.
5. Restart ESC.
6. Provide user User1 token.
7. Provide security password when requested.
8. Security Officer Station UI is shown
9. Click on Enroll a new Card and provide a blank token.
10. Provide valid ldap user name and password, token password.
11. Enrollment is complete.
Using user token able to enroll or format another user token.
Only security officer token should be able to enroll/format other tokens.
I suppose this is working because the user token has certificates signed by the same CA as the Security Officer. We might just need to add some further client auth checking to that UI such that only a Security Officer can get through.
There is already code in the cgi's that implement this UI to check to see if a user is actually a Security Officer. If this check fails , the user should not be allowed to proceed to the Security Officer UI. I've already locally gotten this to work properly.
Created attachment 337122 [details]
Changes to fix this problem.
This patch fixes the perl code that is supposed to check to see if a user entering the Security Officer Workstation UI is actually a security officer.
n order to make this check meaninful, the Security Officer's ldap user must be placed in the group "TUS Officers" This is usually located under the ldap tree:
cn=TUS Officers,ou=Groups,dc=<hostname>-<tps instance name>
Could we have the documentation for Security Officer mode reflect that the security officers have to be put in a certain group in LDAP as described above?
attachment (id=337122) +mharmsen
- fix SVN conflict in dogtag/tps-ui/shared/cgi-bin/sow/cfg.pl
- go to old license text in base/tps/forms/esc/cgi-bin/sow/cfg.pl
- use mozldap6 for Solaris cases in base/tps/forms/esc/cgi-bin/sow/cfg.pl
svn commit -m "SO officer security fix #491227."
At revision 343.
Verified that with the user token unable to login to security officer workstation and perform the so functions.