From: James Brown via pve-devel <pve-devel@lists.proxmox.com>
To: "Fabio Fantoni via pve-devel" <pve-devel@lists.proxmox.com>
Cc: "James Brown" <randomvoidmail@foxmail.com>
Subject: [pve-devel] SPAM: [Security] Arbitrary file reading via malicious VM config
Date: Wed, 27 Nov 2024 08:14:28 +0800 [thread overview]
Message-ID: <mailman.747.1732667455.391.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 5314 bytes --]
From: "James Brown" <randomvoidmail@foxmail.com>
To: "Fabio Fantoni via pve-devel" <pve-devel@lists.proxmox.com>
Subject: SPAM: [Security] Arbitrary file reading via malicious VM config
Date: Wed, 27 Nov 2024 08:14:28 +0800
Message-ID: <tencent_C3D2C670AE0CC99C45BA8C83853D3BDE0205@qq.com>
I suspect a security flaw within ESXi VM import. If a malicious actor forges a VMWare VM config with root paths such as /var/log/auth.log, could lead to potential data leak if the import task is executed.
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-11-27 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 0:14 James Brown via pve-devel [this message]
2024-11-27 0:40 ` [pve-devel] SPAM: [Security] Arbitrary file reading via maliciousVM config James Brown via pve-devel
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=mailman.747.1732667455.391.pve-devel@lists.proxmox.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal