summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'metadata/glsa/glsa-201312-10.xml')
-rw-r--r--metadata/glsa/glsa-201312-10.xml61
1 files changed, 61 insertions, 0 deletions
diff --git a/metadata/glsa/glsa-201312-10.xml b/metadata/glsa/glsa-201312-10.xml
new file mode 100644
index 000000000000..807586ee45cc
--- /dev/null
+++ b/metadata/glsa/glsa-201312-10.xml
@@ -0,0 +1,61 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
+<glsa id="201312-10">
+ <title>libsmi: Arbitrary code execution </title>
+ <synopsis>A buffer overflow in libsmi might allow a context-dependent
+ attacker to execute arbitrary code.
+ </synopsis>
+ <product type="ebuild">libsmi</product>
+ <announced>2013-12-14</announced>
+ <revised count="1">2013-12-14</revised>
+ <bug>342127</bug>
+ <access>local, remote</access>
+ <affected>
+ <package name="net-libs/libsmi" auto="yes" arch="*">
+ <unaffected range="ge">0.4.8-r1</unaffected>
+ <vulnerable range="lt">0.4.8-r1</vulnerable>
+ </package>
+ </affected>
+ <background>
+ <p>libsmi is a library that allows management applications to access SMI
+ MIB module definitions.
+ </p>
+ </background>
+ <description>
+ <p>libsmi contains a buffer overflow vulnerability in the smiGetNode()
+ function in lib/smi.c.
+ </p>
+ </description>
+ <impact type="normal">
+ <p>A context-dependent attacker could possibly execute arbitrary code by
+ way of a specially crafted Object Identifier (OID).
+ </p>
+ </impact>
+ <workaround>
+ <p>There is no known workaround at this time.</p>
+ </workaround>
+ <resolution>
+ <p>All libsmi users should upgrade to the latest version:</p>
+
+ <code>
+ # emerge --sync
+ # emerge --ask --oneshot --verbose "&gt;=net-libs/libsmi-0.4.8-r1"
+ </code>
+
+ <p>Packages which depend on this library may need to be recompiled. Tools
+ such as revdep-rebuild may assist in identifying these packages.
+ </p>
+
+ <p>NOTE: This is a legacy GLSA. Updates for all affected architectures are
+ available since October 30, 2010. It is likely that your system is
+ already no longer affected by this issue.
+ </p>
+ </resolution>
+ <references>
+ <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-2891">CVE-2010-2891</uri>
+ </references>
+ <metadata tag="requester" timestamp="2011-10-07T23:37:09Z">
+ underling
+ </metadata>
+ <metadata tag="submitter" timestamp="2013-12-14T22:33:15Z">Zlogene</metadata>
+</glsa>