#108 Invalid update policy can crash BIND
Closed: Fixed None Opened 11 years ago by pspacek.

Version: a7cae08cacad019852067dd7ecf86cefbe35c70e
Discovered at: 2013-02-14T14:47+0100

Define a zone with following update policy:

grant R.TEST wildcard x*x;

BIND will crash on zone reload (or immediatelly if persistent search is enabled).

BIND throws an error (i.e. do not crash!) when the update policy is used in /etc/named.conf.
Log message:

/etc/named.conf:43: 'x*x' is not a wildcard

Backtrace:

#0  0x00007ffff57dd8a5 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x00007ffff57df085 in abort () at abort.c:92
#2  0x00007ffff7fa8e14 in assertion_failed (file=<value optimized out>, line=<value optimized out>, type=<value optimized out>, cond=<value optimized out>)
    at ./main.c:219
#3  0x00007ffff695d89a in isc_assertion_failed (file=<value optimized out>, line=<value optimized out>, type=<value optimized out>, cond=<value optimized out>)
    at assertions.c:57
#4  0x00007ffff78adfbc in dns_ssutable_addrule (table=0x7ffff23391c8, grant=isc_boolean_true, identity=0x7ffff422fae0, matchtype=2, name=0x7ffff422fcf0, ntypes=0, 
    types=0x0) at ssu.c:174
#5  0x00007ffff20ce45f in acl_configure_zone_ssutable (policy_str=<value optimized out>, zone=0x7fffec2d0ba0) at acl.c:423
#6  0x00007ffff20dabda in ldap_parse_zoneentry (entry=0x7ffff7f2f7b8, inst=0x7ffff2337010) at ldap_helper.c:1292
#7  0x00007ffff20dbc5f in refresh_zones_from_ldap (ldap_inst=0x7ffff2337010, delete_only=<value optimized out>) at ldap_helper.c:1498
#8  0x00007ffff20e1bfe in manager_create_db_instance (mctx=0x7ffff8209250, name=<value optimized out>, argv=0x7ffff7f3bf90, dyndb_args=<value optimized out>)
    at zone_manager.c:182
#9  0x00007ffff20d16ad in dynamic_driver_init (mctx=0x7ffff8209250, name=0x7ffff7f3f1f8 "ipa", argv=0x7ffff7f3bf90, dyndb_args=0x7ffff7f2b510) at ldap_driver.c:1364
#10 0x00007ffff7807de6 in dns_dynamic_db_load (libname=<value optimized out>, name=0x7ffff7f3f1f8 "ipa", mctx=0x7ffff8209250, argv=0x7ffff7f3bf90, 
    dyndb_args=0x7ffff7f2b510) at ./dynamic_db.c:232
#11 0x00007ffff7fc74dc in configure_dynamic_db (view=0x7fffec046e40, config=<value optimized out>, vconfig=<value optimized out>, cachelist=0x7ffff7f3f1f8, 
    bindkeys=0x7ffff7f3f200, mctx=0x7ffff8209250, actx=0x7ffff7f2b070, need_hints=isc_boolean_true) at server.c:1210
#12 configure_view (view=0x7fffec046e40, config=<value optimized out>, vconfig=<value optimized out>, cachelist=0x7ffff7f3f1f8, bindkeys=0x7ffff7f3f200, 
    mctx=0x7ffff8209250, actx=0x7ffff7f2b070, need_hints=isc_boolean_true) at server.c:2784
#13 0x00007ffff7fca7b5 in load_configuration (filename=0x7ffff4232850 "\370\225\365\367\377\177", server=0x7ffff7f36010, first_time=isc_boolean_true) at server.c:4912
#14 0x00007ffff7fcbbb5 in run_server (task=<value optimized out>, event=0x0) at server.c:5381
#15 0x00007ffff697c2f8 in dispatch (uap=0x7ffff7f2d010) at task.c:1012
#16 run (uap=0x7ffff7f2d010) at task.c:1157
#17 0x00007ffff6331851 in start_thread (arg=0x7ffff4233700) at pthread_create.c:301
#18 0x00007ffff589390d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Bug is present also in 2.5 release.

Metadata Update from @pspacek:
- Issue assigned to pspacek
- Issue set to the milestone: Fedora 19

7 years ago

Login to comment on this ticket.

Metadata