From: "Sergey Popov (pinkbyte)" <pinkbyte@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/security/en/glsa: glsa-201406-10.xml
Date: Fri, 13 Jun 2014 20:42:51 +0000 (UTC) [thread overview]
Message-ID: <20140613204251.8207D2004E@flycatcher.gentoo.org> (raw)
pinkbyte 14/06/13 20:42:51
Added: glsa-201406-10.xml
Log:
GLSA 201406-10
Revision Changes Path
1.1 xml/htdocs/security/en/glsa/glsa-201406-10.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/security/en/glsa/glsa-201406-10.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/security/en/glsa/glsa-201406-10.xml?rev=1.1&content-type=text/plain
Index: glsa-201406-10.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/xsl/glsa.xsl" type="text/xsl"?>
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201406-10">
<title>lighttpd: Multiple vulnerabilities</title>
<synopsis>Multiple vulnerabilities have been found in lighttpd, allowing
remote attackers cause a Denial of Service condition or execute arbitrary
SQL statements.
</synopsis>
<product type="ebuild">lighttpd</product>
<announced>June 13, 2014</announced>
<revised>June 13, 2014: 1</revised>
<bug>392581</bug>
<bug>444179</bug>
<bug>490432</bug>
<bug>491154</bug>
<bug>504330</bug>
<access>remote</access>
<affected>
<package name="www-servers/lighttpd" auto="yes" arch="*">
<unaffected range="ge">1.4.35</unaffected>
<vulnerable range="lt">1.4.35</vulnerable>
</package>
</affected>
<background>
<p>lighttpd is a lightweight high-performance web server.</p>
</background>
<description>
<p>Multiple vulnerabilities have been discovered in lighttpd. Please review
the CVE identifiers referenced below for details.
</p>
</description>
<impact type="high">
<p>A remote attacker could create a Denial of Service condition.
Futhermore, a remote attacker may be able to execute arbitrary SQL
statements.
</p>
</impact>
<workaround>
<p>There is no known workaround at this time.</p>
</workaround>
<resolution>
<p>All lighttpd users should upgrade to the latest version:</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=www-servers/lighttpd-1.4.35"
</code>
</resolution>
<references>
<uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-4362">CVE-2011-4362</uri>
<uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2012-5533">CVE-2012-5533</uri>
<uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4508">CVE-2013-4508</uri>
<uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4559">CVE-2013-4559</uri>
<uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4560">CVE-2013-4560</uri>
<uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-2323">CVE-2014-2323</uri>
</references>
<metadata tag="requester" timestamp="Tue, 06 Mar 2012 01:13:56 +0000">craig</metadata>
<metadata tag="submitter" timestamp="Fri, 13 Jun 2014 20:40:42 +0000">ackle</metadata>
</glsa>
reply other threads:[~2014-06-13 20:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140613204251.8207D2004E@flycatcher.gentoo.org \
--to=pinkbyte@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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