February 1, 2020 2:01 PM, "Uwe Werler" wrote:
> Thank you very much Gilles for the insights.
>
> It's not really your fault because it's how our brain works. If we want to
> get things working we
> are concentrating to get them working - not how to break them. It's amazing
> that the code
Am 31. Januar 2020 18:48:51 GMT+00:00 schrieb gil...@poolp.org:
>January 30, 2020 4:44 PM, gil...@poolp.org wrote:
>
>> It depends on your configuration, not all setups are vulnerable.
>>
>> I think I recall your name from the comments on my tutorial and this
>is a
>> setup that would not be
Really great article.
Was very fun to read.
And again thanks for your work on osmtpd, am actually sending from a
server set up from your poolp post :D
Sucks about the bug, but logic errors are the wurst.
Take care.
---
Aisha
blog.aisha.cc
On 2020-01-31 13:48, gil...@poolp.org wrote:
January 30, 2020 4:44 PM, gil...@poolp.org wrote:
> It depends on your configuration, not all setups are vulnerable.
>
> I think I recall your name from the comments on my tutorial and this is a
> setup that would not be vulnerable for example. The bug still exists, but
> it can't be used to
It depends on your configuration, not all setups are vulnerable.
I think I recall your name from the comments on my tutorial and this is a
setup that would not be vulnerable for example. The bug still exists, but
it can't be used to exploit the same code path.
You should update, this is not
Never mind it, its working
On January 30, 2020 4:09:23 PM GMT+01:00, Flipchan wrote:
>Has anyone verified that it writes to disk as the qualysis report says
>?
>
>I have tried on 6.5 and 6.4 but its not writing to disk
>
>
>
>https://www.qualys.com/2020/01/28/cve-2020-7247/lpe-rce-opensmtpd.txt
Has anyone verified that it writes to disk as the qualysis report says ?
I have tried on 6.5 and 6.4 but its not writing to disk
https://www.qualys.com/2020/01/28/cve-2020-7247/lpe-rce-opensmtpd.txt
On January 29, 2020 2:07:38 PM GMT+01:00, Oriol Demaria
wrote:
>I understand that root
January 29, 2020 7:00 PM, "Stuart Henderson" wrote:
>
> I hesitate to mention it in case it puts anyone off from updating (DON'T
> DO THAT, YOU SHOULD UPDATE!) but it is easy to configure to avoid the
> root-escalation aspect of this bug - and many readers will already be
> doing this,
On 2020-01-29, Oriol Demaria wrote:
> I understand that root might be required to open privileged ports, but then
> how commands are run as root when you exploit opensmtpd vulnerability?
For a clue:
ls -l /var/mail
How are those messages delivered to those files with those permissions?
> In
On 2020-01-29 13:07, Oriol Demaria wrote:
> I understand that root might be required to open privileged ports, but then
> how commands are run as root when you exploit opensmtpd vulnerability?
Giles has said further information is coming but it root isn't just required for
privileged ports but
smtpd needs to be able to execute mda with user privileges to deliver mail to
them,
it cannot revoke all its privileges after binding ports. furthermore, mbox
needs to
be able to write to /var/mail forcing it to retain some privileges.
after I'm done dealing with the aftermath, i'll explain in
I understand that root might be required to open privileged ports, but then how
commands are run as root when you exploit opensmtpd vulnerability?
In case someone hasn't seen patch right now your system.
Regards.
--
Oriol Demaria
0x58415679
12 matches
Mail list logo
