8 results (0.005 seconds)

CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 0

18 Jun 2020 — An issue was discovered in adns before 1.5.2. pap_mailbox822 does not properly check st from adns__findlabel_next. Without this, an uninitialised stack value can be used as the first label length. Depending on the circumstances, an attacker might be able to trick adns into crashing the calling program, leaking aspects of the contents of some of its memory, causing it to allocate lots of memory, or perhaps overrunning a buffer. This is only possible with applications which make non-raw queries for SOA or RP ... • http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00037.html • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •

CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 0

18 Jun 2020 — An issue was discovered in adns before 1.5.2. It hangs, eating CPU, if a compression pointer loop is encountered. Se detectó un problema en adns versiones anteriores a 1.5.2. Se cuelga, consumiendo CPU, si un bucle de puntero de compresión es encontrado • http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00037.html • CWE-400: Uncontrolled Resource Consumption •

CVSS: 8.8EPSS: 3%CPEs: 3EXPL: 0

18 Jun 2020 — An issue was discovered in adns before 1.5.2. It corrupts a pointer when a nameserver speaks first because of a wrong number of pointer dereferences. This bug may well be exploitable as a remote code execution. Se detectó un problema en adns versiones anteriores a 1.5.2. Corrompe un puntero cuando un servidor de nombres habla primero debido a un número incorrecto de desreferencias de puntero. • http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=adns.git • CWE-476: NULL Pointer Dereference •

CVSS: 7.5EPSS: 0%CPEs: 3EXPL: 0

18 Jun 2020 — An issue was discovered in adns before 1.5.2. adns_rr_info mishandles a bogus *datap. The general pattern for formatting integers is to sprintf into a fixed-size buffer. This is correct if the input is in the right range; if it isn't, the buffer may be overrun (depending on the sizes of the types on the current platform). Of course the inputs ought to be right. And there are pointers in there too, so perhaps one could say that the caller ought to check these things. • http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=adns.git • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •

CVSS: 7.5EPSS: 0%CPEs: 3EXPL: 0

18 Jun 2020 — An issue was discovered in adns before 1.5.2. It overruns reading a buffer if a domain ends with backslash. If the query domain ended with \, and adns_qf_quoteok_query was specified, qdparselabel would read additional bytes from the buffer and try to treat them as the escape sequence. It would depart the input buffer and start processing many bytes of arbitrary heap data as if it were the query domain. Eventually it would run out of input or find some other kind of error, and declare the query domain invali... • http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=adns.git • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •

CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0

18 Jun 2020 — An issue was discovered in adns before 1.5.2. adnshost mishandles a missing final newline on a stdin read. It is wrong to increment used as well as setting r, since used is incremented according to r, later. Rather one should be doing what read() would have done. Without this fix, adnshost may read and process one byte beyond the buffer, perhaps crashing or perhaps somehow leaking the value of that byte. Se detectó un problema en adns versiones anteriores a 1.5.2. adnshost maneja inapropiadamente una falta ... • http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=adns.git • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •

CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 0

18 Jun 2020 — An issue was discovered in adns before 1.5.2. It fails to ignore apparent answers before the first RR that was found the first time. when this is fixed, the second answer scan finds the same RRs at the first. Otherwise, adns can be confused by interleaving answers for the CNAME target, with the CNAME itself. In that case the answer data structure (on the heap) can be overrun. With this fixed, it prefers to look only at the answer RRs which come after the CNAME, which is at least arguably correct. • http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00037.html • CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer •

CVSS: 7.5EPSS: 0%CPEs: 14EXPL: 1

18 Sep 2008 — GNU adns 1.4 and earlier uses a fixed source port and sequential transaction IDs for DNS requests, which makes it easier for remote attackers to spoof DNS responses, a different vulnerability than CVE-2008-1447. NOTE: the vendor reports that this is intended behavior and is compatible with the product's intended role in a trusted environment. GNU adns 1.4 y versiones anteriores que utilizan un puerto de origen fijo e IDs de transacciones secuenciales, el cual hace más fácil a los atacantes remotos envenenar... • http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492698 • CWE-16: Configuration •