From: Stefan Hanreich <s.hanreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-firewall 1/1] fix #7818: disallow line feeds in firewall comments
Date: Wed, 15 Jul 2026 11:34:30 +0200 [thread overview]
Message-ID: <20260715093432.34437-1-s.hanreich@proxmox.com> (raw)
They do not get sanitized and interpreted literally, allowing for
authenticated users to inject additional lines into the firewall
configuration files.
Signed-off-by: Stefan Hanreich <s.hanreich@proxmox.com>
---
Notes:
Did quickly check the other properties as well, but couldn't find
anything. Will take a closer look still but wanted to get the patch
ready in the meanwhile.
src/PVE/Firewall.pm | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/src/PVE/Firewall.pm b/src/PVE/Firewall.pm
index 93f8c34..894a87b 100644
--- a/src/PVE/Firewall.pm
+++ b/src/PVE/Firewall.pm
@@ -1228,6 +1228,18 @@ sub pve_fw_verify_icmp_type_spec {
return $icmp_type;
}
+PVE::JSONSchema::register_format('pve-fw-comment-spec', \&pve_fw_verify_comment_spec);
+
+sub pve_fw_verify_comment_spec {
+ my ($comment) = @_;
+
+ if ($comment =~ m/[\n\r]/) {
+ die "comment must not contain a line feed\n";
+ }
+
+ return $comment;
+}
+
# helper function for API
sub copy_opject_with_digest {
@@ -1623,6 +1635,7 @@ my $rule_properties = {
description => "Descriptive comment.",
type => 'string',
optional => 1,
+ format => 'pve-fw-comment-spec',
},
'icmp-type' => {
description =>
--
2.47.3
next reply other threads:[~2026-07-15 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 9:34 Stefan Hanreich [this message]
2026-07-15 9:48 ` [PATCH pve-firewall 1/1] fix #7818: disallow line feeds in firewall comments Stoiko Ivanov
2026-07-15 10:11 ` Stefan Hanreich
2026-07-15 10:11 ` superseded: " Stefan Hanreich
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=20260715093432.34437-1-s.hanreich@proxmox.com \
--to=s.hanreich@proxmox.com \
--cc=pve-devel@lists.proxmox.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox