Security issue with Project Specific Landing Area
(Doc ID 2161319.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Enterprise Data Quality - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
You are on EDQ 12.2.1 and have created Project Specific landing areas corresponding to the internal ID of the projects. However, User A with access only to Project A is still able to create a data store and snapshot from files in the landing area of Project B for which they don't have access. This the user does by simply unchecking the project specific landing area checkbox and specifying the path, "\[internal id of Project B\file_name]," assuming User A knows the internal id of Project B overtly or covertly. Please note the 'Add Project' permission is not given to the group to which the user belongs.
This access to other project's landing area needs to be restricted.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document