View Issue Details

IDProjectCategoryView StatusLast Update
0016776CentOS-7unboundpublic2019-11-27 20:55
Reporteragnosys 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version7.5.1804 
Target VersionFixed in Version 
Summary0016776: Crash if ratelimit taken into use with unbound-control
DescriptionUnbound 1.6.6 crashes if ratelimit taken into use with unbound-control instead of with unbound.conf

It is a known bug, corrected in unbound 1.7.3:
https://nlnetlabs.nl/pipermail/unbound-users/2018-June/010714.html
Steps To Reproduce1- Install, configure and start unbound, without activating the ratelimit in config file.
2 - Use unbound-control to set ratelimit to a value greater than 0, while it is not activated in the unbound.conf:

Example:
$ unbound-control set_option ratelimit: 1000

It causes a segfault and unbound crashes immediately:
Nov 27 14:49:23 XXXXXXXX kernel: unbound[20922]: segfault at 8 ip 00005621712d6d21 sp 00007f0c909a6010 error 4 in unbound[56217126b000+109000]
Nov 27 14:49:24 XXXXXXXX systemd: unbound.service: main process exited, code=killed, status=11/SEGV
Nov 27 14:49:24 XXXXXXXX systemd: Unit unbound.service entered failed state.
Nov 27 14:49:24 XXXXXXXX systemd: unbound.service failed.
Additional Informationunbound-1.7.3 has already been successfully pre-packaged for CentOS 8:
https://koji.mbox.centos.org/koji/packageinfo?packageID=2387
TagsNo tags attached.
abrt_hash
URL

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-11-27 20:55 agnosys New Issue