oracle priveleges

Aside from the DBA role privs set in DBA_ROLE_PRIVS, are there any othe rdefault priveleges that are "high risk" if granted to the wrong person, if so can you provide some other dangerous privelege that we should check for and the types of permissions they would allow to the users to do in your database. I guess DBA role is the highest privelege, as SYS and SYSTEM get it?
LVL 4
pma111Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

johnsoneSenior Oracle DBACommented:
Users and/or application roles should never be granted privileges with the word ANY in them.  That also goes for PUBLIC.

Rule of thumb is minimal privileges.  Nobody should have privileges they don't need "just because".  Laziness on the part of developers/designers to determine which privileges are necessary are not an excuse.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
slightwv (䄆 Netminder) Commented:
>> I guess DBA role is the highest privelege, as SYS and SYSTEM get it?

SYSDBA is the highest.

>>that are "high risk" if granted to the wrong person,

I agree with the above post about minimal.  You also need to be aware of some out of the box permissions that might be dangerous.

Sorry but I don't have an exhaustive list nor have I seen one.

For example:  We have to manually revoke execute from PUBLIC on the following packages for every database:
UTL_FILE
DBMS_LOB
DBMS_SQL
DBMS_JOB
DBMS_OBFUSCATION_TOOLKIT
UTL_SMTP
UTL_HTTP
UTL_TCP
DBMS_RANDOM

Then manually grant execute specifically to the users that need them.

The reason:  Many of these have potential 'holes' or outright concerns that might be exploited.
pma111Author Commented:
Thanks - I did have some docs on the packages, I could never really understand why DBMS_RANDOM was a security issue though - can you shed any light? I know some of the others listed allow for access outside the DB and on the OS/file system etc., and I guess some like DBMS_SQL may allow for elevation or priveleges etc, i. basic user running queries under the context of a DBA.
slightwv (䄆 Netminder) Commented:
Never bothered to look it up.  I just follow orders...  ;)

Even if I had Larry Ellison himself tell our security folks that dbms_random is "safe", I would still have to revoke it.

Looks like someone wrote a book on the subject.  From the explanation there, it sounds believable.

https://books.google.com/books?id=KPohQPM8CEYC&pg=PA132&lpg=PA132&dq=security+hole+dbms_random&source=bl&ots=wOGr75Jatk&sig=xrA5hOZsRtqLR-WDukp3yw-Sd-Q&hl=en&sa=X&ei=bNVZVfKcJYKCyQSgh4GACQ&ved=0CB4Q6AEwAA#v=onepage&q=security%20hole%20dbms_random&f=false

Is it "true"?  It has to be, I found it on the Internet...
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.