Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Security-Basics
[Top] [All Lists]

RE: Storing doc pdfs within an application or database?

Subject: RE: Storing doc pdfs within an application or database?
Date: Mon, 21 Jan 2008 13:01:24 -0500
WALI,

This is an example of improper file level permissions.

It appears that the admins need to add a step when an employee arrives.
That step being to change the inherited permissions on the files.


Kind Regards,

Scott Ramsdell
CISSP CCNA MSCE



-----Original Message-----
From: listbounce@securityfocus.com [mailto:listbounce@securityfocus.com]
On Behalf Of WALI
Sent: Sunday, January 20, 2008 10:41 AM
To: security-basics@securityfocus.com
Subject: Storing doc pdfs within an application or database?

An in house developed application related to Human resources, developed 
using ASP (not asp.net) using Oracle 9i as backend, serves employees
payroll 
and tracks their development. Part of each of the employees HR homepage 
(viewable on the web browser)  pertains to storing their employment 
contract, their educational certificates, passport copies of their and
their 
family spouses etc., in either pdf or doc format.

These files (pdf and doc) are stored in a shared folder on the same
server 
hosting the application.

The problem is, there is 'security by obscurity' only. If I am savvy
enough 
to use an application proxy or even dig through my browser history, I
can 
find the whole URL relating to that document, as an example:
Visited: 
Administrator@http://abcint/Administration/Employment_Contract_HR2006/23
13441.pdf

where, 'abcint' is the Netbios name of the server and starting 
'Administration' onwards is the webshare on the same server.

2313441.pdf is my employment contract number where the series of number
is 
easily identifiable for it's my employee ID too.

Now, I can change that serial and *poof*, get to see any other pdf too, 
relating to another employee.

How do you guys take care of such authorisation/aunthentication
mechanism 
when it comes to pdf/doc files that are not residing within a database? 



<Prev in Thread] Current Thread [Next in Thread>