Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When evaluating attached xccdf with --results-arf option, but without --results, oscap segfaults.

Version-Release number of selected component (if applicable):
openscap-1.2.12-1.el7.x86_64

How reproducible:
Should be realiable

Steps to Reproduce:
1. fetch oval, xccdf and sce.sh file
2.  oscap xccdf eval --results-arf arf.xml xccdf.xml
3.

Actual results:
segfault

Expected results:
program finishes successfully.

Additional info:

Created attachment 1234413 [details]
xccdf file

Created attachment 1234414 [details]
sce file

Created attachment 1234415 [details]
oval file

Actually I have confused myself - it segfaults even with --results. So the issue is NOT about having --results-arf used alone.

This is caused by affected/@family="posix" which is not a valid value.

That said, I don't think we should segfault in these cases so I have proposed a fix upstream: https://github.com/OpenSCAP/openscap/pull/616

Verified.

NEW:
[0 root@qeos-33 ~]# rpm -qa openscap
openscap-1.2.14-1.el7.x86_64

[0 root@qeos-33 ~]# oscap xccdf eval --results-arf arf.xml xccdf.xml
Title
Rule    xccdf_moc.elpmaxe.www_rule_1
Result  pass

Title
Rule    xccdf_moc.elpmaxe.www_rule_2
Result  notchecked


OLD:
[root@qeos-40 ~]# rpm -qa openscap
openscap-1.2.10-2.el7.x86_64   

[root@qeos-40 ~]# oscap xccdf eval --results-arf arf.xml xccdf.xml
Title
Rule    xccdf_moc.elpmaxe.www_rule_1
Result  pass

Title
Rule    xccdf_moc.elpmaxe.www_rule_2
Result  notchecked 

Segmentation fault

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2291