From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: [PATCH] fix handling of zero length domain names in dn_expand
Date: Thu, 4 Sep 2014 19:07:27 +0200 [thread overview]
Message-ID: <20140904170726.GC10361@port70.net> (raw)
In-Reply-To: <20140904095039.496f5810@ncopa-desktop.alpinelinux.org>
[-- Attachment #1: Type: text/plain, Size: 439 bytes --]
* Natanael Copa <ncopa@alpinelinux.org> [2014-09-04 09:50:39 +0200]:
> On Wed, 13 Aug 2014 10:21:41 +0200
> Natanael Copa <ncopa@alpinelinux.org> wrote:
>
> > Copy a zero length string instead of returning error when trying to
> > expand a zero lentgh domain name (null terminator).
> >
> Rich pointed out to me on IRC that this will not write terminating '\0'
> when domain name length is zero. I'll send new patch.
>
here is a patch
[-- Attachment #2: 0001-fix-empty-name-handling-in-dn_expand.patch --]
[-- Type: text/x-diff, Size: 1753 bytes --]
From 49b96b160fdde9218bcaffa196ca9e6d5a233094 Mon Sep 17 00:00:00 2001
From: Szabolcs Nagy <nsz@port70.net>
Date: Thu, 4 Sep 2014 18:29:16 +0200
Subject: [PATCH] fix empty name handling in dn_expand
Empty name was rejected in dn_expand since commit
56b57f37a46dab432247bf29d96fcb11fbd02a6d
which is a regression as reported by Natanael Copa.
But it turns out only an "uncompressed" empty name was rejected,
if an offset pointer is used to represent an empty name then
dn_expand failed to null terminate the returned name.
this fix makes dn_expand accept and return empty names correctly.
---
src/network/dn_expand.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/src/network/dn_expand.c b/src/network/dn_expand.c
index 849df19..4fa6af8 100644
--- a/src/network/dn_expand.c
+++ b/src/network/dn_expand.c
@@ -6,7 +6,7 @@ int __dn_expand(const unsigned char *base, const unsigned char *end, const unsig
const unsigned char *p = src;
char *dend = dest + (space > 254 ? 254 : space);
int len = -1, i, j;
- if (p==end || !*p) return -1;
+ if (p==end) return -1;
/* detect reference loop using an iteration counter */
for (i=0; i < end-base; i+=2) {
if (*p & 0xc0) {
@@ -16,11 +16,13 @@ int __dn_expand(const unsigned char *base, const unsigned char *end, const unsig
if (j >= end-base) return -1;
p = base+j;
} else if (*p) {
- j = *p+1;
- if (j>=end-p || j>dend-dest) return -1;
- while (--j) *dest++ = *++p;
- *dest++ = *++p ? '.' : 0;
+ j = *p++;
+ if (j >= end-p || j >= dend-dest) return -1;
+ while (j--) *dest++ = *p++;
+ if (*p) *dest++ = '.';
} else {
+ if (dest == dend) return -1;
+ *dest = 0;
if (len < 0) len = p+1-src;
return len;
}
--
1.7.10.4
next prev parent reply other threads:[~2014-09-04 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 8:21 Natanael Copa
[not found] ` <20140904095039.496f5810@ncopa-desktop.alpinelinux.org>
2014-09-04 17:07 ` Szabolcs Nagy [this message]
2014-09-04 18:11 ` Szabolcs Nagy
2014-09-04 20:20 ` Rich Felker
2014-09-04 22:15 ` Szabolcs Nagy
2014-09-04 22:41 ` Rich Felker
2014-09-04 20:22 ` Natanael Copa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140904170726.GC10361@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).