From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] fix WebUI system information leak
Date: Mon, 04 Sep 2017 12:35:00 +0100 [thread overview]
Message-ID: <1504524900.5011.3.camel@ipfire.org> (raw)
In-Reply-To: <20170903161453.1e018d7c.peter.mueller@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]
Merged.
-Michael
On Sun, 2017-09-03 at 16:14 +0200, Peter Müller wrote:
> Disable unauthenticated access to cgi-bin/credits.cgi. The page
> leaks the currently installed version of IPFire and the hardware
> architecture.
>
> Both information might make a successful attack much easier.
>
> This issue can be reproduced by accessing https://[IPFire-IP]:444/cgi-bin/credits.cgi
> and accepting a SSL certificate warning (if any).
>
> Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> ---
> diff --git a/config/httpd/vhosts.d/ipfire-interface-ssl.conf b/config/httpd/vhosts.d/ipfire-interface-ssl.conf
> index daac75742..4897d56d2 100644
> --- a/config/httpd/vhosts.d/ipfire-interface-ssl.conf
> +++ b/config/httpd/vhosts.d/ipfire-interface-ssl.conf
> @@ -42,10 +42,6 @@
> Satisfy Any
> Allow from All
> </Files>
> - <Files credits.cgi>
> - Satisfy Any
> - Allow from All
> - </Files>
> <Files dial.cgi>
> Require user admin
> </Files>
> diff --git a/config/httpd/vhosts.d/ipfire-interface.conf b/config/httpd/vhosts.d/ipfire-interface.conf
> index 8783c632b..c7c05972e 100644
> --- a/config/httpd/vhosts.d/ipfire-interface.conf
> +++ b/config/httpd/vhosts.d/ipfire-interface.conf
> @@ -34,10 +34,6 @@
> Satisfy Any
> Allow from All
> </Files>
> - <Files credits.cgi>
> - Satisfy Any
> - Allow from All
> - </Files>
> <Files dial.cgi>
> Require user admin
> </Files>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-09-04 11:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 14:14 Peter Müller
2017-09-04 11:35 ` Michael Tremer [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=1504524900.5011.3.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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