bind vulnerabilities (SUSE)
122 vulnerabilities.
bindSUSEParsing large DNS messages may cause excessive CPU load7.5 HighbindSUSEA stack exhaustion flaw in control channel code may cause named to terminate unexpectedly7.5 HighbindSUSEExceeding the recursive-clients quota may cause named to terminate unexpectedly when stale-answer-client-timeout is set to 07.5 HighbindSUSEnamed's configured cache size limit can be significantly exceeded7.5 HighbindSUSEGrafana is an open-source platform for monitoring and observability. Starting with the 9.1...4.2 MediumbindSUSEStored XSS in Graphite FunctionDescription tooltip6.2 MediumbindSUSEnamed configured to answer from stale cache may terminate unexpectedly at recursive-clients soft quota7.5 HighbindSUSEnamed configured to answer from stale cache may terminate unexpectedly while processing RRSIG queries7.5 HighbindSUSEAn UPDATE message flood may cause named to exhaust all available memory7.5 HighbindSUSEPrometheus Exporter Toolkit vulnerable to basic authentication bypass6.2 MediumbindSUSEDenial of service via crafted Accept-Language header in golang.org/x/text/language7.5 HighbindSUSEMemory exhaustion when compiling regular expressions in regexp/syntax7.5 HighbindSUSEGrafana folders admin only permission privilege escalation7.6 HighbindSUSEMemory leaks in EdDSA DNSSEC verification code7.5 HighbindSUSEMemory leak in ECDSA DNSSEC verification code7.5 HighbindSUSEBIND 9 resolvers configured to answer from stale cache with zero stale-answer-client-timeout may terminate unexpectedly7.5 HighbindSUSEProcessing large delegations may severely degrade resolver performance5.3 MediumbindSUSEAuthentication Bypass in Grafana via auth proxy allowing escalation from admin to server admin6.6 MediumbindSUSEgolang.org/x/net/http2 Denial of Service vulnerability7.5 HighbindSUSEGrafana account takeover via OAuth vulnerability7.1 HighbindSUSEStored XSS in Grafana's Unified Alerting7.3 HighbindSUSEPrototype Pollution in async7.8 HighbindSUSEDoS from specifically crafted TCP packets5.3 MediumbindSUSEDNS forwarders - cache poisoning vulnerability6.8 MediumbindSUSEExposure of Private Personal Information to an Unauthorized Actor in follow-redirects/follow-redirects8.0 HighbindSUSEPrototype Pollution in kriszyp/json-schema9.8 CriticalbindSUSELame cache can be abused to severely degrade resolver performance5.3 MediumbindSUSEInefficient Regular Expression Complexity in chalk/ansi-regex7.5 HighbindSUSEA second vulnerability in BIND's GSSAPI security policy negotiation can be targeted by a buffer overflow attack8.1 HighbindSUSEAn assertion check can fail while answering queries for DNAME records that require the DNAME to be processed to resolve itself7.5 HighbindSUSEA broken inbound incremental zone update (IXFR) can cause named to terminate unexpectedly6.5 MediumbindSUSESecurity update for bindNo scorebindSUSEA vulnerability in BIND's GSSAPI security policy negotiation can be targeted by a buffer overflow attack8.1 HighbindSUSERegular Expression Denial of Service (ReDoS)7.5 HighbindSUSEupdate-policy rules of type "subdomain" are enforced incorrectly4.3 MediumbindSUSEA flaw in native PKCS#11 code can lead to a remotely triggerable assertion failure in pk11.c7.5 HighbindSUSEA truncated TSIG response can lead to an assertion failure6.5 MediumbindSUSEAttempting QNAME minimization after forwarding can lead to an assertion failure in resolver.c7.5 HighbindSUSEIn BIND 9.15.6 -> 9.16.5, 9.17.0 -> 9.17.3, An attacker who can establish a TCP connection with...7.5 HighbindSUSEA buffer boundary check assertion in rdataset.c can fail incorrectly during zone transfer4.9 MediumbindSUSEA buffer boundary check assertion in rdataset.c can fail incorrectly during zone transfer4.9 MediumbindSUSEA logic error in code which checks TSIG validity can be used to trigger an assertion failure in tsig.c7.5 HighbindSUSEBIND does not sufficiently limit the number of fetches performed when processing referrals8.6 HighbindSUSETCP-pipelined queries can bypass tcp-clients limit7.5 HighbindSUSEA race condition when discarding malformed packets can cause BIND to exit with an assertion failure5.9 MediumbindSUSELimiting simultaneous TCP clients was ineffective7.5 HighbindSUSEZone transfer controls for writable DLZ zones were not effective5.3 MediumbindSUSEAn assertion failure can occur if a trust anchor rolls over to an unsupported key algorithm when using managed-keys4.9 MediumbindSUSEUpdate policies krb5-subdomain and ms-subdomain do not enforce controls promised in their documentation6.5 MediumbindSUSEA flaw in the "deny-answer-aliases" feature can cause an assertion failure in named7.5 High- Show moreLoading…