diff options
author | V3n3RiX <venerix@redcorelinux.org> | 2017-10-09 18:53:29 +0100 |
---|---|---|
committer | V3n3RiX <venerix@redcorelinux.org> | 2017-10-09 18:53:29 +0100 |
commit | 4f2d7949f03e1c198bc888f2d05f421d35c57e21 (patch) | |
tree | ba5f07bf3f9d22d82e54a462313f5d244036c768 /metadata/glsa/glsa-200512-17.xml |
reinit the tree, so we can have metadata
Diffstat (limited to 'metadata/glsa/glsa-200512-17.xml')
-rw-r--r-- | metadata/glsa/glsa-200512-17.xml | 69 |
1 files changed, 69 insertions, 0 deletions
diff --git a/metadata/glsa/glsa-200512-17.xml b/metadata/glsa/glsa-200512-17.xml new file mode 100644 index 000000000000..13e53784914b --- /dev/null +++ b/metadata/glsa/glsa-200512-17.xml @@ -0,0 +1,69 @@ +<?xml version="1.0" encoding="utf-8"?> +<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd"> +<glsa id="200512-17"> + <title>scponly: Multiple privilege escalation issues</title> + <synopsis> + Local users can exploit an scponly flaw to gain root privileges, and + scponly restricted users can use another vulnerability to evade shell + restrictions. + </synopsis> + <product type="ebuild">scponly</product> + <announced>2005-12-29</announced> + <revised>2006-05-22: 02</revised> + <bug>116526</bug> + <access>local and remote</access> + <affected> + <package name="net-misc/scponly" auto="yes" arch="*"> + <unaffected range="ge">4.2</unaffected> + <vulnerable range="lt">4.2</vulnerable> + </package> + </affected> + <background> + <p> + scponly is a restricted shell, allowing only a few predefined commands. + It is often used as a complement to OpenSSH to provide access to remote + users without providing any remote execution privileges. + </p> + </background> + <description> + <p> + Max Vozeler discovered that the scponlyc command allows users to chroot + into arbitrary directories. Furthermore, Pekka Pessi reported that + scponly insufficiently validates command-line parameters to a scp or + rsync command. + </p> + </description> + <impact type="high"> + <p> + A local attacker could gain root privileges by chrooting into arbitrary + directories containing hardlinks to setuid programs. A remote scponly + user could also send malicious parameters to a scp or rsync command + that would allow to escape the shell restrictions and execute arbitrary + programs. + </p> + </impact> + <workaround> + <p> + There is no known workaround at this time. + </p> + </workaround> + <resolution> + <p> + All scponly users should upgrade to the latest version: + </p> + <code> + # emerge --sync + # emerge --ask --oneshot --verbose ">=net-misc/scponly-4.2"</code> + </resolution> + <references> + <uri link="http://sublimation.org/scponly/index.html#relnotes">scponly release notes</uri> + <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-4532">CVE-2005-4532</uri> + <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-4533">CVE-2005-4533</uri> + </references> + <metadata tag="submitter" timestamp="2005-12-27T09:38:39Z"> + koon + </metadata> + <metadata tag="bugReady" timestamp="2005-12-29T10:10:38Z"> + koon + </metadata> +</glsa> |