Details
Description
here are no controls over which files SYSCS_EXPORT_TABLE can write, thus allowing any user that has permission to execute the procedure to try and modufy information that they have no permissions to do.
In a similar fashion to the one described in DERBY-2436 I could overwrite derby.properties at least leaqding to a dnial of service attack on the next re-boot.
With more time it might be possible to write out a valid properties file which would allow chaning the authentication, silentaly adding a new user etc.
Attachments
Issue Links
- is related to
-
DERBY-2436 SYSCS_IMPORT_TABLE can be used to read derby files
- Open