Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-web2py: security bump to version 2.14.6
Date: Wed, 26 Apr 2017 09:11:10 +0200	[thread overview]
Message-ID: <87pofzod81.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170425134423.3313-1-peter@korsgaard.com> (Peter Korsgaard's message of "Tue, 25 Apr 2017 15:44:23 +0200")

>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:

 > CVE-2016-4806 - Web2py versions 2.14.5 and below was affected by Local File
 > Inclusion vulnerability, which allows a malicious intended user to
 > read/access web server sensitive files.

 > CVE-2016-4807 - Web2py versions 2.14.5 and below was affected by Reflected
 > XSS vulnerability, which allows an attacker to perform an XSS attack on
 > logged in user (admin).

 > CVE-2016-4808 - Web2py versions 2.14.5 and below was affected by CSRF (Cross
 > Site Request Forgery) vulnerability, which allows an attacker to trick a
 > logged in user to perform some unwanted actions i.e An attacker can trick an
 > victim to disable the installed application just by sending a URL to victim.

 > CVE-2016-10321 - web2py before 2.14.6 does not properly check if a host is
 > denied before verifying passwords, allowing a remote attacker to perform
 > brute-force attacks.

 > Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-04-26  7:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 13:44 [Buildroot] [PATCH] python-web2py: security bump to version 2.14.6 Peter Korsgaard
2017-04-26  7:11 ` Peter Korsgaard [this message]
2017-04-28 12:26 ` Peter Korsgaard

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=87pofzod81.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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