-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please add password protection when updating the database #155
Comments
I'm sorry, but I cannot follow. What application or vulnerability are you talking about?
If this issue is actually about adding password protection for the AIDE database please adjust the issue title accordingly. |
a similar situation will be for the tripwire program, where if a password is required and its input is required to write data to a file, but the virus will not be able to go beyond the 5th point
this is the vulnerability it is equivalent to the fact that you have an account without a password. I don't understand how you haven't done protection yet as in a similar tripwire program |
A password protection of the database simply gives you a false sense of security. If an experienced attacker has full (aka root) access to the machine, they can for example simply exchange the binary to generate a new database file and forged reports; or they exchange your $SHELL binary, the kernel or some libraries to rig the behaviour of the tool. Apart from that, there is an open feature request for database and configuration signing (see #7); but this feature also won't help you entirely with this attack vector.
Your title suggests that there is a vulnerability (within AIDE) that gives you full access to a machine. This is plain wrong and misleading. Hence I changed the issue title now. Additionally I close this issue as |
there is another attack vector. If two people have access to the server, then someone can install a malicious program and go unnoticed because the program can record data without knowing the password. I agree that you need to be able to sign the settings file and database as you said in this ticket #7 I ask you to provide an attack vector when the password protects not only from an attack from the outside, but also from an attack when several legitimate users have access to the server. |
As said above, if someone has root access to the server, they don't need to know the database or signing password; they can simply alter other parts of the OS (like your shell or the kernel) to hide their activities and replace the aide binary to generate forged reports. |
but this is much more difficult to do if there is a password to protect. Unnecessary actions for a hacker, especially if he is poorly prepared, will help to become an obstacle |
if the application gets full access to the server through the vulnerability, then this application will be able to update the AIDE database and write new files to the system as if they were always there. to do this, the program will simply restart your program in manual mode and update the data. you do not have protection in the form of a password that you need to enter when changing the database. take an example from the tripwire program, there is higher protection.
Please add password protection when updating the database
The text was updated successfully, but these errors were encountered: