[ http://issues.apache.org/jira/browse/DERBY-1056?page=all ]
Kathey Marsden updated DERBY-1056:
----------------------------------
Summary: Print a security warning to derby.log and network server
console if network server is started with remote connections enabled and
security manager, user authentication, and ecrypted userid are not on (was:
Print a security warning to derby.log and network server console if network
server is started with -h 0.0.0.0 and security manager, user authentication,
and ecrypted userid are not on)
Description:
Information and questions from the user list seem to indicate that often users
enable remote connections by starting network server with the -h 0.0.0.0 or
-h <machinename> option without taking proper security measures. I think it
would be worthwhile to print a security warning the console and derby.log if
network server is starated without the proper security in place.
Serious security issues exist when starting network server and allowing remote
connections unless users:
- Run in security manager with permissions restricted as much as possible.
- Enable user authentication
- Use encrypted userid/password (Currently only available with IBMJCE)
- Maybe also print a warning if bootPassword is sent in the
connectionAttributes, since this cannot be encrypted. (I had thought there was
a jira issue for this but can't find it.)
Even when started with the localhost default there can be security issues if
the machine itself is not secure.
An example of such an attack might include creating databases until the host
machine disk filled up, deleting all user data etc.
Related issues:
DERBY-65
DERBY-474
DERBY -528
DERBY-962
was:
Information and questions from the user list seem to indicate that often users
start network server with the -h 0.0.0.0 option without taking proper security
measures. I think it would be worthwhile to print a security warning the
console and derby.log if network server is starated without the proper security
in place.
Serious security issues exist when starting network server with the -h 0.0.0.0
option unless users
- Run in security manager with permissions restricted as much as possible.
- Enable user authentication
- Use encrypted userid/password (Currently only available with IBMJCE)
Even when started with the localhost default there can be security issues if
the machine itself is not secure.
An example of such an attack might include creating databases until the host
machine disk filled up, deleting all user data etc.
Related issues:
DERBY-65
DERBY-474
DERBY -528
DERBY-962
Dan pointed out that this needs to print when remote connections are enabled
with -h <machinename> as well so changing the title.
I also thought of one other warning needed if bootPassword is passed in the
connection attributes, so added that to the description.
Also Dan asked me to elaborate about security issues when Network Server is
started on localhost. Mostly these arise from shared machines where users do
not trust each other, for example the District Attourney and the Public
Defender share a machine and have separate databases but these are
accessesed through network server. The same risks apply because the users
of the machine do not trust each other. The D.A. might set up his database
and user authentication for the database and think he is all set, but really
the password is being sent CLEAR_TEXT and the public defender might be able to
gain access.
The D.A might even think he could set up a bootPassword, but that has two
problems 1) The bootPassword is sent in the connection attributes and so is
always sent clear text and 2) once the database is booted the public defender
has access.
Perhaps this type of risk is just obvious, but because we don't start up with
connections restricted in anyway as they might be with other database servers,
users may not realize the risk.
Some of these issues were discussed in this thread:
http://www.nabble.com/DRDA-Password-Encryption-%28SECMEC_EUSRIDPWD-and-SECMEC_USRENCPWD%29-t80296.html#a24266
At that time David suggested making a top level Client/Server Security Issue
which is not a bad idea, but we actually have not had much luck executing on
other such important top level issues as DERBY-310 and DERBY-209. Since this
one is security it might gain more attention. I don't know.
> Print a security warning to derby.log and network server console if network
> server is started with remote connections enabled and security manager, user
> authentication, and ecrypted userid are not on
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1056
> URL: http://issues.apache.org/jira/browse/DERBY-1056
> Project: Derby
> Type: Improvement
> Components: Network Server, Security
> Reporter: Kathey Marsden
> Fix For: 10.2.0.0
>
> Information and questions from the user list seem to indicate that often
> users enable remote connections by starting network server with the -h
> 0.0.0.0 or -h <machinename> option without taking proper security measures.
> I think it would be worthwhile to print a security warning the console and
> derby.log if network server is starated without the proper security in place.
> Serious security issues exist when starting network server and allowing
> remote connections unless users:
> - Run in security manager with permissions restricted as much as possible.
> - Enable user authentication
> - Use encrypted userid/password (Currently only available with IBMJCE)
> - Maybe also print a warning if bootPassword is sent in the
> connectionAttributes, since this cannot be encrypted. (I had thought there
> was a jira issue for this but can't find it.)
> Even when started with the localhost default there can be security issues
> if the machine itself is not secure.
> An example of such an attack might include creating databases until the host
> machine disk filled up, deleting all user data etc.
> Related issues:
> DERBY-65
> DERBY-474
> DERBY -528
> DERBY-962
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
