Risk 1/5 · Low
0001-add-support-for-user-flags.patch
Result #2789
Comment
Risk is low. The patch only adds support for reading user-supplied flags from a per-user config file and appending them to the browser launch command. There is no network access, privilege escalation, persistence, or packaging-time execution introduced. The main security consideration is that the new code performs unquoted word splitting on $VIVALDI_USER_FLAGS when invoking vivaldi-bin, so a malicious or malformed config file can inject arbitrary command-line arguments into the browser process. However, this is explicitly user-controlled input in the user's own config directory, not a supply-chain or package compromise. No high-severity issue is evident in this diff alone.
@@ -1,18 +1,18 @@
-From 68c2dec905a7c88895c458dd40708ab9989385cf Mon Sep 17 00:00:00 2001
+From 091faff8c4249e5e5e06b83370350776281bbf54 Mon Sep 17 00:00:00 2001
From: BlackEagle <ike.devolder@gmail.com>
Date: Wed, 19 Jan 2022 20:57:58 +0100
Subject: [PATCH] add support for user flags
Signed-off-by: BlackEagle <ike.devolder@gmail.com>
---
- vivaldi-stable | 9 ++++++++-
+ vivaldi | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
-diff --git a/vivaldi-stable b/vivaldi-stable
-index 5b5f1bf..8e95859 100755
---- a/vivaldi-stable
-+++ b/vivaldi-stable
-@@ -53,6 +53,13 @@ export CHROME_VERSION_EXTRA="stable"
+diff --git a/vivaldi b/vivaldi
+index 2f87883..b8fe8a0 100755
+--- a/vivaldi
++++ b/vivaldi
+@@ -117,6 +117,13 @@ export CHROME_VERSION_EXTRA="stable"
# We don't want bug-buddy intercepting our crashes. http://crbug.com/24120
export GNOME_DISABLE_CRASH_DIALOG=SET_BY_GOOGLE_CHROME