summaryrefslogtreecommitdiff
path: root/metadata/glsa/glsa-201701-34.xml
diff options
context:
space:
mode:
authorV3n3RiX <venerix@redcorelinux.org>2017-10-09 18:53:29 +0100
committerV3n3RiX <venerix@redcorelinux.org>2017-10-09 18:53:29 +0100
commit4f2d7949f03e1c198bc888f2d05f421d35c57e21 (patch)
treeba5f07bf3f9d22d82e54a462313f5d244036c768 /metadata/glsa/glsa-201701-34.xml
reinit the tree, so we can have metadata
Diffstat (limited to 'metadata/glsa/glsa-201701-34.xml')
-rw-r--r--metadata/glsa/glsa-201701-34.xml50
1 files changed, 50 insertions, 0 deletions
diff --git a/metadata/glsa/glsa-201701-34.xml b/metadata/glsa/glsa-201701-34.xml
new file mode 100644
index 000000000000..8a0167229212
--- /dev/null
+++ b/metadata/glsa/glsa-201701-34.xml
@@ -0,0 +1,50 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
+<glsa id="201701-34">
+ <title>runC: Privilege escalation</title>
+ <synopsis>A vulnerability in runC could lead to privilege escalation.</synopsis>
+ <product type="ebuild">runc</product>
+ <announced>2017-01-12</announced>
+ <revised>2017-01-12: 1</revised>
+ <bug>605378</bug>
+ <access>remote</access>
+ <affected>
+ <package name="app-emulation/runc" auto="yes" arch="*">
+ <unaffected range="ge">1.0.0_rc2-r2</unaffected>
+ <vulnerable range="lt">1.0.0_rc2-r2</vulnerable>
+ </package>
+ </affected>
+ <background>
+ <p>RunC is a CLI tool for spawning and running containers according to the
+ OCI specification.
+ </p>
+ </background>
+ <description>
+ <p>A vulnerability was discovered in runC that allows additional container
+ processes via ‘runc exec’ to be ptraced by the pid 1 of the
+ container. This allows the main processes of the container, if running
+ as root, to gain access to file-descriptors of these new processes.
+ </p>
+ </description>
+ <impact type="normal">
+ <p>An attacker, who is able to successfully escape the container or modify
+ runC’s state before process initialization, could escalate privileges.
+ </p>
+ </impact>
+ <workaround>
+ <p>There is no known workaround at this time.</p>
+ </workaround>
+ <resolution>
+ <p>All runC users should upgrade to the latest version:</p>
+
+ <code>
+ # emerge --sync
+ # emerge --ask --oneshot --verbose "&gt;=app-emulation/runc-1.0.0_rc2-r2"
+ </code>
+ </resolution>
+ <references>
+ <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9962">CVE-2016-9962</uri>
+ </references>
+ <metadata tag="requester" timestamp="2017-01-12T13:07:29Z">b-man</metadata>
+ <metadata tag="submitter" timestamp="2017-01-12T22:52:16Z">b-man</metadata>
+</glsa>