Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Sat, 14 Jan 2023 22:56:28 +0000
From: Barry Bond <>
To: "" <>
Subject: Behavior change in getaddrbyname() with AF_UNSPEC

This is related to this change: made back in 2020.

In the repro case, getaddrbyname() with AF_UNSPEC sends out two requests, but only gets back a single response, with the ipv4 address.   There is no ipv6 on the network.

name_from_dns() contains the relevant code.  After __res_msend_rc() returns, 'nq' is 2, and 'alens' is [96, 0], indicating that there was an ipv4 response of 96 bytes, but no response for ipv6.  Then the validation code runs:

                for (i=0; i<nq; i++) {
                                if (alens[i] < 4 || (abuf[i][3] & 15) == 2) return EAI_AGAIN;
                                if ((abuf[i][3] & 15) == 3) return 0;
                                if ((abuf[i][3] & 15) != 0) return EAI_FAIL;

and the result is EAI_AGAIN, because alens[1]==0.

Before this patch, the code would have parsed the ipv4 response via __dns_parse(), failed to parse the empty second response because alens[1]<12, and the function would return with ctx.cnt==1.

I propose adding one new check at the top of the for() loop:
                if (alens[i] == 0) continue; /* response timed out */

Barry - Microsoft Azure Sphere

Content of type "text/html" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.