Your message dated Fri, 18 Jan 2008 15:47:04 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#461069: fixed in python-cherrypy 2.2.1-3.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: python-cherrypy
Version: 2.2.1-3
Severity: grave
Tags: security patch
Hi,
the following CVE (Common Vulnerabilities & Exposures) id was
published for python-cherrypy.
CVE-2008-0252[0]:
| Directory traversal vulnerability in the _get_file_path function in
| (1) lib/sessions.py in CherryPy 3.0.x up to 3.0.2, (2)
| filter/sessionfilter.py in CherryPy 2.1, and (3)
| filter/sessionfilter.py in CherryPy 2.x allows remote attackers to
| create or delete arbitrary files, and possibly read and write portions
| of arbitrary files, via a crafted session id in a cookie.
You can find a patch for this on:
http://www.cherrypy.org/changeset/1775
If you fix this vulnerability please also include the CVE id
in your changelog entry.
For further information:
[0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0252
Kind regards
Nico
--
Nico Golde - http://www.ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.
pgpCuUliPMIG9.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-cherrypy
Source-Version: 2.2.1-3.1
We believe that the bug you reported is fixed in the latest version of
python-cherrypy, which is due to be installed in the Debian FTP archive:
python-cherrypy_2.2.1-3.1.diff.gz
to pool/main/p/python-cherrypy/python-cherrypy_2.2.1-3.1.diff.gz
python-cherrypy_2.2.1-3.1.dsc
to pool/main/p/python-cherrypy/python-cherrypy_2.2.1-3.1.dsc
python-cherrypy_2.2.1-3.1_all.deb
to pool/main/p/python-cherrypy/python-cherrypy_2.2.1-3.1_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nico Golde <[EMAIL PROTECTED]> (supplier of updated python-cherrypy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 18 Jan 2008 16:25:39 +0100
Source: python-cherrypy
Binary: python-cherrypy
Architecture: source all
Version: 2.2.1-3.1
Distribution: unstable
Urgency: high
Maintainer: Gustavo Noronha Silva <[EMAIL PROTECTED]>
Changed-By: Nico Golde <[EMAIL PROTECTED]>
Description:
python-cherrypy - Python web development framework
Closes: 461069
Changes:
python-cherrypy (2.2.1-3.1) unstable; urgency=high
.
* Non-maintainer upload by security team.
* This update addresses the following security issue:
- Directory traversal vulnerability in the _get_file_path function
in filter/sessionfilter.py allows remote attackers to create or
delete arbitrary files, and possibly read and write portions of
arbitrary files, via a crafted session id in a cookie
(CVE-2008-0252; Closes: #461069).
Files:
73ffb1d64656c5c1141e236fa5811cae 818 python optional
python-cherrypy_2.2.1-3.1.dsc
89d9de9656065c79ac7e1fb7c6cb073f 5530 python optional
python-cherrypy_2.2.1-3.1.diff.gz
f753b6034a0c9cb4ca339ca93ae54f74 220648 python optional
python-cherrypy_2.2.1-3.1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHkMkNHYflSXNkfP8RAlMrAKCMzgMavjxugfwhTUi3grcfsfiZ5wCfa7QB
sxcThqrWqUXIFx5rJThakvE=
=psKV
-----END PGP SIGNATURE-----
--- End Message ---
