Your message dated Fri, 16 Jun 2006 12:31:50 +0300
with message-id <[EMAIL PROTECTED]>
and subject line done
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: dokuwiki
Version: 0.0.20060309-3
Severity: critical
Another security flaw that I was informed about through freshmeat.
Cheers,
-Hilko
-------------------- Start of forwarded message --------------------
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: [fmII] Privilege Escalation Problem in DokuWiki
Message-Id: <[EMAIL PROTECTED]>
Date: Tue, 6 Jun 2006 11:27:20 -0700 (PDT)
This is an email sent to you by the owners of the freshmeat.net project
record for DokuWiki. All URLs and other useful information can be found
at
http://freshmeat.net/projects/dokuwiki/
________________________| Subscriber message |_________________________
Sent by: Andreas Gohr
http://freshmeat.net/~agohr/
Hello again!
Just two days after the last security problem another flaw was discovered.
Luckily not as bad as the last one.
Andreas Åkre Solberg discovered a security flaw which allows registered
users to view page content they usually have no access to. The problem is
in the way how a successful user profile change is handled.
This affects only installs which have Access Control Lists enabled (off by
default) and restricted the READ permission for certain pages even for
logged in users. Non-authenticated users can not exploit this bug.
The package available at http://www.splitbrain.org/go/dokuwiki was updated
again to reflect the change but fixing it manually is simple, too. Info on
how to do this is available at
http://bugs.splitbrain.org/?do=details&id=825
Andi
PS: I apologize for the trouble. Unfortunately the bigger and complex a
software gets the more likely security flaws are. I try hard to avoid
common mistakes but sometimes a bug slips through. If you are an
experienced PHP developer I encourage you to have a look at the code
(preferably the devel code) your self to help spotting such weaknesses -
the more people check, the better it gets.
__________________________| End of message |___________________________
-------------------- End of forwarded message --------------------
--- End Message ---
--- Begin Message ---
Version: 0.0.20060309-4
--- End Message ---
