From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top
Cc: Matej Hrica <mhrica@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH v2 5/5] conf: Use the right maximum buffer size for c->sock_path
Date: Thu, 27 Jun 2024 22:46:41 +0200 [thread overview]
Message-ID: <20240627204641.4046184-6-sbrivio@redhat.com> (raw)
In-Reply-To: <20240627204641.4046184-1-sbrivio@redhat.com>
UNIX_SOCK_MAX is the maximum number we'll append to the socket path
if we generate it automatically. If it's given on the command line,
it can be up to UNIX_PATH_MAX (including the terminating character)
long.
UNIX_SOCK_MAX happened to kind of fit because it's 100 (instead of
108).
Commit ceddcac74a6e ("conf, tap: False "Buffer not null terminated"
positives, CWE-170") fixed the wrong problem: the right fix for the
problem at hand was actually commit cc287af173ca ("conf: Fix
incorrect bounds checking for sock_path parameter").
Fixes: ceddcac74a6e ("conf, tap: False "Buffer not null terminated" positives, CWE-170")
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
---
conf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conf.c b/conf.c
index 9e47e9a..3c38ceb 100644
--- a/conf.c
+++ b/conf.c
@@ -1398,7 +1398,7 @@ void conf(struct ctx *c, int argc, char **argv)
c->foreground = 1;
break;
case 's':
- ret = snprintf(c->sock_path, UNIX_SOCK_MAX - 1, "%s",
+ ret = snprintf(c->sock_path, sizeof(c->sock_path), "%s",
optarg);
if (ret <= 0 || ret >= (int)sizeof(c->sock_path))
die("Invalid socket path: %s", optarg);
--
@@ -1398,7 +1398,7 @@ void conf(struct ctx *c, int argc, char **argv)
c->foreground = 1;
break;
case 's':
- ret = snprintf(c->sock_path, UNIX_SOCK_MAX - 1, "%s",
+ ret = snprintf(c->sock_path, sizeof(c->sock_path), "%s",
optarg);
if (ret <= 0 || ret >= (int)sizeof(c->sock_path))
die("Invalid socket path: %s", optarg);
--
2.43.0
next prev parent reply other threads:[~2024-06-27 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 20:46 [PATCH v2 0/5] Small, assorted "hardening" fixes Stefano Brivio
2024-06-27 20:46 ` [PATCH v2 1/5] conf: Copy up to MAXDNSRCH - 1 bytes, not MAXDNSRCH Stefano Brivio
2024-06-27 20:46 ` [PATCH v2 2/5] tcp_splice: Check return value of setsockopt() for SO_RCVLOWAT Stefano Brivio
2024-06-27 20:46 ` [PATCH v2 3/5] util, lineread, tap: Overflow checks on long signed sums and subtractions Stefano Brivio
2024-06-27 20:46 ` [PATCH v2 4/5] tap: Discard guest data on length descriptor mismatch Stefano Brivio
2024-06-27 20:46 ` Stefano Brivio [this message]
2024-06-29 9:36 ` [PATCH v2 5/5] conf: Use the right maximum buffer size for c->sock_path David Gibson
2024-07-02 20:54 ` [PATCH v2 0/5] Small, assorted "hardening" fixes Stefano Brivio
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=20240627204641.4046184-6-sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=mhrica@redhat.com \
--cc=passt-dev@passt.top \
/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://passt.top/passt
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 IMAP folder(s).