[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACHAsRfd1PupvP+aEJ9=UbVtx6pBKRLyeSiQ3khcrycPa1Ef6g@mail.gmail.com>
Date: Tue, 8 Jan 2013 16:16:48 -0300
From: WHK Yan <yan.uniko.102@...il.com>
To: Kurt Seifried <kseifried@...hat.com>
Cc: oss-security@...ts.openwall.com,
Carlos Alberto Lopez Perez <clopez@...lia.com>, submissions@...ketstormsecurity.com,
mr.inj3ct0r@...il.com, submit@...ecurity.com, vuln@...unia.com,
vuldb@...urityfocus.com
Subject: Re: Re: [Full-disclosure] File Disclosure in
SimpleMachines Forum <= 2.0.3
The type and range of user defined smf, a co-manager can be created by an
administrator setting custom permissions, does not mean it comes by default.
Anyway in some groups smf computer security using caution and have had this in
our case was a very dangerous.
2013/1/8 Kurt Seifried <kseifried@...hat.com>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01/08/2013 06:36 AM, WHK Yan wrote:
> > The flaw is not exploitable without privileges. On some occasions
> > there are forums where there are co-admistrators which have
> > privileges to view the error log but not to modify code or at least
> > read the mysql connection.
>
> So is a trust/security boundary crossed here? Can you please confirm
> that the co-admistrator (or anyone) is not supposed to be able to read
> arbitrary files accessible to the web server, and that this attack
> does indeed allow that? Thanks.
>
> Removing full-disclosure@...ts.grok.org.uk from CC due to reply spam.
>
>
> - --
> Kurt Seifried Red Hat Security Response Team (SRT)
> PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iQIcBAEBAgAGBQJQ7G9iAAoJEBYNRVNeJnmTPD0P/3qP0sPDl82+V1ST02WalH7q
> O4qhaSWUi//rY3RXMARDVfNUOeTfzBgOpS21/4qeLuLH07ko5rrwGOksuc6U8fE+
> NOQz9A3sqHQyE0419WqWDuI/kIK7SucWnGw8ACU+/vckvzWjfSDRQamq6+P+SBxL
> Cf8zS65JY5kMTRgOPK4HMy/UyUgye9DTg49aKoUIzDndbzEX+BIvr6LqSPzh5wTE
> +/NbA9R20ARFGJSe/gQARTVs8d5p0/6oi9KSxcwHLfvpWEC1zNsziVpervI3doNB
> SXb9DoiGH/G0GGoryVP5tl2kgzuaMWgdys/ypHDZ+Jmap4DsV161+Y1pS8UcRP4f
> MRAKZ3Slb/1wyW7omRnA/J6EWrgyEq4Z0f14DPUhLiLMaOgIHbVEt/b/pfyRYdPE
> EEhbemCqzqaQMwSkN9g8XSOptwD2g2vj01Kdi58TzKvS4zZefHnmVCUmfr31fEF6
> iuh4FH4baYygNlyqMMH83QtSHEB6YwRGky/bMxFZ+FGOPq0amYXBhiqV/dAkS2Ns
> +Tt0dpJCIBo4e6TMOmFe4obpYj4XSlRVz0SKiU4oz5XvDKUiKEM1Q4DGrLtY2+9W
> 1ozv7vcKFdg89Vrm/i9BfAiyLue9swXtr5LFS1PAE5HJB6yWBSERv2PPvnX4xj3i
> PMcisy0d8xjsEbxA4rxG
> =d5Kh
> -----END PGP SIGNATURE-----
>
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
