Bug 1533845

Summary: aide crashes or hangs on corrupted/fuzzed database file
Product: [Fedora] Fedora Reporter: Karel Srot <ksrot>
Component: aideAssignee: Radovan Sroka <rsroka>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: high    
Version: 27CC: dkopecek, rsroka, sgrubb
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-30 22:23:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
reproducers to crash or hang aide none

Description Karel Srot 2018-01-12 11:17:42 UTC
Created attachment 1380398 [details]
reproducers to crash or hang aide

Description of problem:

Using the AFL fuzzer I did generated several files that make aide to crash or hang.

Version-Release number of selected component (if applicable):
aide-0.16-4.fc27.x86_64

How reproducible:
always

Steps to Reproduce:
1. use following config file

@@define DBDIR /var/lib/aide
@@define LOGDIR /var/log/aide
database=file:@@{DBDIR}/aide.db
database_out=file:@@{DBDIR}/aide.db.new
gzip_dbout=no
verbose=5
report_url=file:@@{LOGDIR}/aide.log
report_url=stdout
NORMAL = sha256
/etc/aide.conf   NORMAL

2. copy any of the files from the archive to /var/lib/aide/aide.db
3. aide -C

Actual results:
segfault, hang,...

Expected results:
error printed, no hang or segfault

Additional info:
Sorry for not categorizing the reproducers, they could be multiple causing the same issue. I hope I would be able to do it later.

Comment 2 Ben Cotton 2018-11-27 14:48:44 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2018-11-30 22:23:36 UTC
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.