From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: James Brown <randomvoidmail@foxmail.com>,
Fabio Fantoni via pve-devel <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Arbitrary file reading via malicious VM config
Date: Wed, 27 Nov 2024 09:15:15 +0100 [thread overview]
Message-ID: <54ebb9f5-01ff-4943-a077-618a687bdbfb@proxmox.com> (raw)
In-Reply-To: <03e65d1b-2c75-4a8e-8d4a-82d3511c5c23@proxmox.com>
Am 27.11.24 um 09:09 schrieb Thomas Lamprecht:
> The core assumption is that the admin doing the import fully controls both sides,
> VMWare ESXi and Proxmox VE.
> As otherwise this feature makes no sense, if the ESXi isn't trusted, it can do all
> sorts of bad things that just cannot be protected against, like e.g., inject some
> rootkits into the VM data stream at any time. And yes, it might also leak some
> data from the PVE host.
btw. what I forgot: This is not really special to the ESXi "storage" that can be
used for import, but any storage attached through network in general.
There is no definitive way to check all potential problems in a race-free way.
But stating that core assumptions one more time explicitly definitively won't
hurt for our docs.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-27 8:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_C3D2C670AE0CC99C45BA8C83853D3BDE0205@qq.com>
2024-11-27 8:09 ` Thomas Lamprecht
2024-11-27 8:15 ` Thomas Lamprecht [this message]
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=54ebb9f5-01ff-4943-a077-618a687bdbfb@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=randomvoidmail@foxmail.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