You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2007/08/14 01:13:30 UTC
[jira] Assigned: (GERONIMO-3404) Using a Null Username allows
access to a running 2.0 server
[ https://issues.apache.org/jira/browse/GERONIMO-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks reassigned GERONIMO-3404:
--------------------------------------
Assignee: David Jencks
> Using a Null Username allows access to a running 2.0 server
> -----------------------------------------------------------
>
> Key: GERONIMO-3404
> URL: https://issues.apache.org/jira/browse/GERONIMO-3404
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security
> Affects Versions: 2.0
> Environment: Released geronimo-tomcat6-jee5-2.0-bin.zip on WinXP and on Linux
> Reporter: Donald Woods
> Assignee: David Jencks
> Priority: Critical
> Fix For: 2.0.x, 2.1
>
> Attachments: GERONIMO-3404.patch
>
>
> I was just testing the geronimo-tomcat6-jee5-2.0-bin.zip on a new WinXP machine and discovered that anyone can administer a Geronimo server (local or remotely) if they enter a null Username when prompted by the deploy or geronimo scripts. I verified that the <user_home>\.geronimo-deployer file did not exist on the WinXP machine and on a Linux box I used to verify the remote scenario....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.