public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pierre-Yves Rofes (py)" <py@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/security/en/glsa: glsa-200712-02.xml
Date: Wed, 05 Dec 2007 22:34:22 +0000	[thread overview]
Message-ID: <E1J02ow-000369-Ss@stork.gentoo.org> (raw)

py          07/12/05 22:34:22

  Added:                glsa-200712-02.xml
  Log:
  GLSA 200712-02

Revision  Changes    Path
1.1                  xml/htdocs/security/en/glsa/glsa-200712-02.xml

file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/glsa/glsa-200712-02.xml?rev=1.1&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/security/en/glsa/glsa-200712-02.xml?rev=1.1&content-type=text/plain

Index: glsa-200712-02.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="200712-02">
  <title>Cacti: SQL injection</title>
  <synopsis>
    An SQL injection vulnerability has been discovered in Cacti.
  </synopsis>
  <product type="ebuild">cacti</product>
  <announced>December 05, 2007</announced>
  <revised>December 05, 2007: 01</revised>
  <bug>199509</bug>
  <access>remote</access>
  <affected>
    <package name="net-analyzer/cacti" auto="yes" arch="*">
      <unaffected range="ge">0.8.6j-r7</unaffected>
      <unaffected range="ge">0.8.7a</unaffected>
      <vulnerable range="lt">0.8.7a</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    Cacti is a complete web-based frontend to rrdtool.
    </p>
  </background>
  <description>
    <p>
    It has been reported that the "local_graph_id" variable used in the
    file graph.php is not properly sanitized before being processed in an
    SQL statement.
    </p>
  </description>
  <impact type="normal">
    <p>
    A remote attacker could send a specially crafted request to the
    vulnerable host, possibly resulting in the execution of arbitrary SQL
    code.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All Cacti users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose &quot;&gt;=net-analyzer/cacti-0.8.6j-r7&quot;</code>
  </resolution>
  <references>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6035">CVE-2007-6035</uri>
  </references>
  <metadata tag="requester" timestamp="Sun, 02 Dec 2007 22:34:20 +0000">
    p-y
  </metadata>
  <metadata tag="bugReady" timestamp="Sun, 02 Dec 2007 22:34:29 +0000">
    p-y
  </metadata>
  <metadata tag="submitter" timestamp="Tue, 04 Dec 2007 22:01:32 +0000">
    p-y
  </metadata>
</glsa>



-- 
gentoo-commits@gentoo.org mailing list



             reply	other threads:[~2007-12-05 22:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 22:34 Pierre-Yves Rofes (py) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-12-05 22:37 [gentoo-commits] gentoo commit in xml/htdocs/security/en/glsa: glsa-200712-02.xml Pierre-Yves Rofes (py)

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=E1J02ow-000369-Ss@stork.gentoo.org \
    --to=py@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