From: Sune Kloppenborg Jeppesen <jaervosz@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Cc: bugtraq@securityfocus.com, full-disclosure@lists.grok.org.uk,
security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 200609-16 ] Tikiwiki: Arbitrary command execution
Date: Tue, 26 Sep 2006 18:06:47 +0200 [thread overview]
Message-ID: <200609261806.53170.jaervosz@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2894 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 200609-16
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: High
Title: Tikiwiki: Arbitrary command execution
Date: September 26, 2006
Bugs: #145714
ID: 200609-16
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Tikiwiki contains a cross-site scripting (XSS) vulnerability as well as
a second vulnerability which may allow remote execution of arbitrary
code.
Background
==========
Tikiwiki is a web-based groupware and content management system,
developed with PHP, ADOdb and Smarty.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 www-apps/tikiwiki < 1.9.5 >= 1.9.5
Description
===========
A vulnerability in jhot.php allows for an unrestricted file upload to
the img/wiki/ directory. Additionally, an XSS exists in the highlight
parameter of tiki-searchindex.php.
Impact
======
An attacker could execute arbitrary code with the rights of the user
running the web server by uploading a file and executing it via a
filepath parameter. The XSS could be exploited to inject and execute
malicious script code or to steal cookie-based authentication
credentials, potentially compromising the victim's browser.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Tikiwiki users should upgrade to the latest version:
# emerge --sync
# emerge --oneshot --verbose --ask ">=www-apps/tikiwiki-1.9.5"
References
==========
[ 1 ] CVE-2006-4299
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4299
[ 2 ] CVE-2006-4602
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4602
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
http://security.gentoo.org/glsa/glsa-200609-16.xml
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
http://bugs.gentoo.org.
License
=======
Copyright 2006 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
http://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2006-09-26 16:34 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=200609261806.53170.jaervosz@gentoo.org \
--to=jaervosz@gentoo.org \
--cc=bugtraq@securityfocus.com \
--cc=full-disclosure@lists.grok.org.uk \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security-alerts@linuxsecurity.com \
/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