public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pbs-devel] [RFC PATCH proxmox-backup] server/rest: disallow non-protected api calls in privileged environment
Date: Tue, 2 Mar 2021 18:02:14 +0100	[thread overview]
Message-ID: <c0c95fb1-cb93-b59e-6ca6-95081966cd85@proxmox.com> (raw)
In-Reply-To: <20210302153120.31213-1-d.csapak@proxmox.com>

On 02.03.21 16:31, Dominik Csapak wrote:
> to prevent potential abuse of non-protected api calls as root
> 

this breaks important CLI tools using client::connect_to_localhost
i.e., proxmox-backup-manager and proxmox-tape and maybe others which
connect still manually.

> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> this is a rather theoretical security improvement, i am not sure if we
> want this? it would only guard against an unprotected api call that somehow

no, such stuff only tends to break things while not providing any value...
lets keep theoretical security improvements also theoretical..

> allows code execution. this could then be abused to connect to the
> daemon and reabuse the same api call, but with root permissions

with magically generating a ticket and circumventing permission checks
how exactly?

> 
> also if we want this, maybe this would be good to have in pve too?

no


> 
>  src/server/rest.rs | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/src/server/rest.rs b/src/server/rest.rs
> index 9bf494fd..6b170b7f 100644
> --- a/src/server/rest.rs
> +++ b/src/server/rest.rs
> @@ -750,6 +750,9 @@ async fn handle_request(
>  
>                      let result = if api_method.protected && env_type == RpcEnvironmentType::PUBLIC {
>                          proxy_protected_request(api_method, parts, body, peer).await
> +                    } else if !api_method.protected && env_type == RpcEnvironmentType::PRIVILEGED {
> +                        let err = http_err!(FORBIDDEN, "invalid server request");
> +                        return Ok((formatter.format_error)(err));
>                      } else {
>                          handle_api_request(rpcenv, api_method, formatter, parts, body, uri_param).await
>                      };
> 





  reply	other threads:[~2021-03-02 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 15:31 Dominik Csapak
2021-03-02 17:02 ` Thomas Lamprecht [this message]
2021-03-03  7:07   ` Thomas Lamprecht
2021-03-03  7:27     ` Dominik Csapak
2021-03-03  8:22       ` Thomas Lamprecht

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=c0c95fb1-cb93-b59e-6ca6-95081966cd85@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=pbs-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal