From: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
To: jayatheerthkulkarni2005@gmail.com
Cc: git@vger.kernel.org, joliss42@gmail.com, joliss@gmail.com,
gitster@pobox.com, peff@peff.net
Subject: [PATCH v2] refspec: safely parse refspecs outside a repository
Date: Sun, 22 Mar 2026 08:05:57 +0530 [thread overview]
Message-ID: <20260322023557.15907-1-jayatheerthkulkarni2005@gmail.com> (raw)
In-Reply-To: <20260321194653.24513-1-jayatheerthkulkarni2005@gmail.com>
When a remote helper like git-remote-http is invoked outside of a
repository (for example, by running `git ls-remote -h <url>` in a
non-git directory), `the_hash_algo` is left uninitialized (NULL).
If a user has a global fetch refspec configured, `parse_refspec()`
attempts to check if the LHS of the refspec is an exact OID by
evaluating `llen == the_hash_algo->hexsz`. Because `the_hash_algo`
is NULL, this results in a segmentation fault. This crash occurs for
both standard and negative refspecs.
Fix this by ensuring `the_hash_algo` is non-NULL before checking
`the_hash_algo->hexsz` for both standard and negative refspecs.
When operating outside a repository, fetching is impossible,
so bypassing the exact OID check is the cleanest approach.
Additionally, while looking into the remote-curl execution path,
take the opportunity to remove an unused `#include "git-curl-compat.h"`
from `remote-curl.c`.
Reported-by: Jo Liss <joliss@gmail.com>
Helped-by: Jeff King <peff@peff.net>
Signed-off-by: K Jayatheerth <jayatheerthkulkarni2005@gmail.com>
---
Changes in v2:
Instead of adding a fix by giving a default hash like we did in cmd_apply()
I understood that it is impossible to fetch here.
Therefore I picked up whatever Peff suggested here.
Since I got no feedback on the test, I am assuming it is correct and leaving as is.
refspec.c | 4 ++--
remote-curl.c | 1 -
t/t5551-http-fetch-smart.sh | 15 +++++++++++++++
3 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/refspec.c b/refspec.c
index 0775358d96..a864a0bac2 100644
--- a/refspec.c
+++ b/refspec.c
@@ -84,7 +84,7 @@ static int parse_refspec(struct refspec_item *item, const char *refspec, int fet
*/
if (!*item->src)
return 0; /* negative refspecs must not be empty */
- else if (llen == the_hash_algo->hexsz && !get_oid_hex(item->src, &unused))
+ else if (the_hash_algo && llen == the_hash_algo->hexsz && !get_oid_hex(item->src, &unused))
return 0; /* negative refpsecs cannot be exact sha1 */
else if (!check_refname_format(item->src, flags))
; /* valid looking ref is ok */
@@ -101,7 +101,7 @@ static int parse_refspec(struct refspec_item *item, const char *refspec, int fet
/* LHS */
if (!*item->src)
; /* empty is ok; it means "HEAD" */
- else if (llen == the_hash_algo->hexsz && !get_oid_hex(item->src, &unused))
+ else if (the_hash_algo && llen == the_hash_algo->hexsz && !get_oid_hex(item->src, &unused))
item->exact_sha1 = 1; /* ok */
else if (!check_refname_format(item->src, flags))
; /* valid looking ref is ok */
diff --git a/remote-curl.c b/remote-curl.c
index 92e40bb682..280880e54e 100644
--- a/remote-curl.c
+++ b/remote-curl.c
@@ -2,7 +2,6 @@
#define DISABLE_SIGN_COMPARE_WARNINGS
#include "git-compat-util.h"
-#include "git-curl-compat.h"
#include "config.h"
#include "environment.h"
#include "gettext.h"
diff --git a/t/t5551-http-fetch-smart.sh b/t/t5551-http-fetch-smart.sh
index 73cf531580..ed81e6b49b 100755
--- a/t/t5551-http-fetch-smart.sh
+++ b/t/t5551-http-fetch-smart.sh
@@ -782,4 +782,19 @@ test_expect_success 'tag following always works over v0 http' '
test_cmp expect actual
'
+test_expect_success 'ls-remote outside repo does not segfault with fetch refspec' '
+ GIT_CEILING_DIRECTORIES=$(pwd) &&
+ export GIT_CEILING_DIRECTORIES &&
+ mkdir nongit &&
+ (
+ cd nongit &&
+ env GIT_CONFIG_NOSYSTEM=1 \
+ GIT_CONFIG_GLOBAL=/dev/null \
+ GIT_CONFIG_COUNT=1 \
+ GIT_CONFIG_KEY_0=remote.origin.fetch \
+ GIT_CONFIG_VALUE_0="+refs/tags/*:refs/tags/*" \
+ git ls-remote "$HTTPD_URL/smart/repo.git"
+ )
+'
+
test_done
--
2.53.0
next prev parent reply other threads:[~2026-03-22 2:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 19:11 remote-curl: segfault parsing remote.<name>.fetch outside a repository Jo Liss
2026-03-21 19:46 ` [PATCH] remote-curl: set fallback hash algorithm outside repo K Jayatheerth
2026-03-21 23:09 ` brian m. carlson
2026-03-22 2:35 ` K Jayatheerth [this message]
2026-03-22 3:31 ` [PATCH v2] refspec: safely parse refspecs outside a repository Junio C Hamano
2026-03-22 3:53 ` Jeff King
2026-03-22 5:36 ` [PATCH v3 1/2] " K Jayatheerth
2026-03-22 5:36 ` [PATCH v3 2/2] refspec: fix typo in comment K Jayatheerth
2026-03-23 22:27 ` [PATCH v3 1/2] refspec: safely parse refspecs outside a repository Junio C Hamano
2026-03-23 23:10 ` Jeff King
2026-03-23 23:39 ` Junio C Hamano
2026-03-24 1:57 ` [PATCH v4 1/2] remote-curl: fall back to default hash outside repo K Jayatheerth
2026-03-24 1:57 ` [PATCH v4 2/2] refspec: fix typo in comment K Jayatheerth
2026-03-24 4:25 ` [PATCH v4 1/2] remote-curl: fall back to default hash outside repo Junio C Hamano
2026-03-21 21:06 ` remote-curl: segfault parsing remote.<name>.fetch outside a repository Jeff King
2026-03-22 1:20 ` Junio C Hamano
2026-03-22 1:37 ` Jeff King
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=20260322023557.15907-1-jayatheerthkulkarni2005@gmail.com \
--to=jayatheerthkulkarni2005@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=joliss42@gmail.com \
--cc=joliss@gmail.com \
--cc=peff@peff.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox