ISC BIND 9.

named configured to answer from stale cache may terminate unexpectedly at recursive-clients soft quota

• ISC BIND 9
• Denial of service

named configured to answer from stale cache may terminate unexpectedly while processing RRSIG queries

• ISC BIND 9
• CWE-20

named may terminate unexpectedly when processing ECS options in repeated responses to iterative queries

• ISC BIND 9
• Denial of service

An UPDATE message flood may cause named to exhaust all available memory

• ISC BIND 9
• Denial of service

An error in QNAME minimization code can cause BIND to exit with an assertion failure

• ISC BIND 9

A flaw in mirror zone validity checking can allow zone data to be spoofed

• ISC BIND 9

A race condition when discarding malformed packets can cause BIND to exit with an assertion failure

• ISC BIND 9

An error in the nxdomain redirect feature can cause BIND to exit with an INSIST assertion failure in query.c

• ISC BIND 9

Zone transfer controls for writable DLZ zones were not effective

• ISC BIND 9

An assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys

• ISC BIND 9

A specially crafted packet can cause named to leak memory

• ISC BIND 9

Limiting simultaneous TCP clients was ineffective

• ISC BIND 9

Update policies krb5-subdomain and ms-subdomain do not enforce controls promised in their documentation

• ISC BIND 9

A flaw in the "deny-answer-aliases" feature can cause an assertion failure in named

• ISC BIND 9

Some versions of BIND can improperly permit recursive query service to unauthorized clients

• ISC BIND 9

BIND 9.12's serve-stale implementation can cause an assertion failure in rbtdb.c or other undesirable behavior, even if serve-stale is not enabled.

• ISC BIND 9

A malformed request can trigger an assertion failure in badcache.c

• ISC BIND 9

Improper fetch cleanup sequencing in the resolver can cause named to crash

• ISC BIND 9

An error in TSIG authentication can permit unauthorized dynamic updates

• ISC BIND 9

An error in TSIG authentication can permit unauthorized zone transfers

• ISC BIND 9

Windows service and uninstall paths are not quoted when BIND is installed

• ISC BIND 9

An error processing RPZ rules can cause named to loop endlessly after handling a query

• ISC BIND 9

named exits with a REQUIRE assertion failure if it receives a null command string on its control channel

• ISC BIND 9

A response packet can cause a resolver to terminate when processing an answer containing a CNAME or DNAME

• ISC BIND 9

An error handling synthesized records could cause an assertion failure when using DNS64 with "break-dnssec yes;"

• ISC BIND 9

Combination of DNS64 and RPZ Can Lead to Crash

• ISC BIND 9

An error handling certain queries using the nxdomain-redirect feature could cause a REQUIRE assertion failure in db.c

• ISC BIND 9