request about Log4j attack attempts and NGINX logs meaning
Mauro,
Unless you use somewhere in your stack log4j vulnerable software (nginx
is not) I don't see anything significant to worry about.
Maxim
On 29.12.2021 21:34, Mauro Tridici wrote:
> Helo Maxim,
>
> thank you
Hello Maxim,
Thank you for your reply.
This is the information that I need :)
Mauro
> On 30 Dec 2021, at 08:20, Maxim Konovalov wrote:
>
> Mauro,
>
> Unless you use somewhere in your stack log4j vulnerable software (nginx is
> not) I don't see anything significant to worry about.
>
> Maxim
Mauro,
Unless you use somewhere in your stack log4j vulnerable software (nginx
is not) I don't see anything significant to worry about.
Maxim
On 29.12.2021 21:34, Mauro Tridici wrote:
Helo Maxim,
thank you very much for the explanation.
In your opinion, is this the case to “fix” this
will feed your server firewall IPs to block in real time. I prefer to
> have total control.
>
>
>
>
>
> Original Message
>
>
> From: mauro.trid...@cmcc.it
> Sent: December 29, 2021 10:30 AM
> To: nginx@nginx.org
> Reply-to: nginx@nginx.org
er firewall IPs to block in real time. I prefer to have
total control.
Original Message
From: mauro.trid...@cmcc.it
Sent: December 29, 2021 10:30 AM
To: nginx@nginx.org
Reply-to: nginx@nginx.org
Subject: Re: [EXTERNAL] Help request about Log4j attack attempts and NGINX logs
meaning
Helo Maxim,
thank you very much for the explanation.
In your opinion, is this the case to “fix” this behaviour (but I don’t know
how, I’m a newbie, sorry) or I should simply ignore it?
Many thanks again,
Mauro
> On 29 Dec 2021, at 19:29, Maxim Dounin wrote:
>
> Hello!
>
> On Wed, Dec 29,
gt;> pocket change for them.
>>
>> I will leave it up to the gurus to parse the log.
>>
>>
>>
>>
>>
>>
>>Original Message
>>
>>
>> From: mauro.trid...@cmcc.it
>> Sent: December 29, 2021 6:55 AM
Hello!
On Wed, Dec 29, 2021 at 03:55:35PM +0100, Mauro Tridici wrote:
> I have an old instance of NGINX (v.1.10.1) running as proxy
> server on a dedicated hardware platform.
> Since the proxy service is reachable from internet, it is
> constantly exposed to cyber attacks.
> In my particular
pocket change for them.
>
> I will leave it up to the gurus to parse the log.
>
>
>
>
>
>
> Original Message
>
>
> From: mauro.trid...@cmcc.it
> Sent: December 29, 2021 6:55 AM
&
> Original Message
>
>
> From: mauro.trid...@cmcc.it
> Sent: December 29, 2021 6:55 AM
> To: nginx@nginx.org
> Reply-to: nginx@nginx.org
> Subject: Help request about Log4j attack attempts and NGINX logs meaning
>
>
>
>
> Dear Users,
>
the log.
Original Message
From: mauro.trid...@cmcc.it
Sent: December 29, 2021 6:55 AM
To: nginx@nginx.org
Reply-to: nginx@nginx.org
Subject: Help request about Log4j attack attempts and NGINX logs meaning
Dear Users,
I have an old instance of NGINX (v.1.10.1) running
Dear Users,
I have an old instance of NGINX (v.1.10.1) running as proxy server on a
dedicated hardware platform.
Since the proxy service is reachable from internet, it is constantly exposed to
cyber attacks.
In my particular case, it is attacked by a lot of Log4j attack attempts from
several
12 matches
Mail list logo