Bug 254401 - CVE-2005-1924 CVE-2006-4169 Multiple arbitrary code execution vulnerabilities
CVE-2005-1924 CVE-2006-4169 Multiple arbitrary code execution vulnerabilities
Product: Fedora
Classification: Fedora
Component: squirrelmail (Show other bugs)
All All
medium Severity high
: ---
: ---
Assigned To: Martin Bacovsky
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-08-25 16:01 EDT by Jay Miller
Modified: 2008-06-16 22:14 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-16 22:14:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jay Miller 2007-08-25 16:01:51 EDT
Description of problem:
The G/PGP (GPG) Plugin 2.1 and earlier for Squirrelmail allow remote
authenticated users to execute arbitrary commands via shell metacharacters in
(1) the fpr parameter to the deleteKey function in gpg_keyring.php, as called by
(a) import_key_file.php, (b) import_key_text.php, and (c) keyring_main.php; and
(2) the keyserver parameter to the gpg_recv_key function in
gpg_key_functions.php, as called by gpg_options.php. NOTE: this issue may
overlap CVE-2007-3636.

Multiple directory traversal vulnerabilities in the G/PGP (GPG) Plugin 2.0, and
2.1dev before 20070614, for Squirrelmail allow remote authenticated users to
include and execute arbitrary local files via a .. (dot dot) in the help
parameter to (1) gpg_help.php or (2) gpg_help_base.php.
Actual results:
Arbitrary code execution

Additional info: I am unsure as to if Fedora has patched this vulnerability, and
don't know if the latest upstream release has fixed this as I have found no
exploits. I don't want a bug to go under the Fedora team's nose.
Comment 1 Tomas 2007-10-24 04:25:16 EDT
I suspect that Fedora's SquirrelMail packages do not include SquirrelMail GPG
plugin. Bug is filed in wrong place.
Comment 2 Bug Zapper 2008-05-14 10:06:23 EDT
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 3 Bug Zapper 2008-06-16 22:14:07 EDT
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.