[DERBY-3532] Invalid & possibly skipped authentication handling when shutting down the network server.

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 10.4.1.3, 10.5.1.1
• Component/s: Network Server
• Labels: derby_triage10_9
• Urgency: Normal
• Bug behavior facts: Security
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 13/Mar/08 20:35
• Updated: 13/Jun/13 22:07

Description

In NetworkServerControlImpl.checkShutdownPrivileges() code fetches the internal authentication service to perform user authentication.

However if no such authentication service is found (null is returned) then authentication is bypassed, this has the potential of being a security hole.

The discussion in DERBY-2109 indicated that even with authentication NONE, there is still an internal authentication service, thus null is not a valid return when getting the internal authentication service. A secure fail safe system would be to not bypass authentication if null is returned.

I tried removing the check for null in the method and that lead to NullPointerExceptions. This means that something wrong is going on and very possibly no authentication checks are actually being made when shutting down the network server.

The null return might be due to checking the authentication after Derby has been shutdown.

Issue Links

• is related to: DERBY-3541 quit; on ij with authentication enabled does not shutdown the derby modules that are loaded
• relates to: DERBY-2109 System privileges