in reply to Re^2: Log4Shell and Log::Log4perl
in thread Log4Shell and Log::Log4perl

As noted in the docs it's possible to disable this behavior with: 

Log::Log4perl::Config->allow_code(0);

[download]

The cake is a lie.
The cake is a lie.
The cake is a lie.

Replies are listed 'Best First'.
Re^4: Log4Shell and Log::Log4perl
by afoken (Chancellor) on Dec 28, 2021 at 13:54 UTC

    As noted in the docs it's possible to disable this behavior with:

    Log::Log4perl::Config->allow_code(0);

    [download]

    So it's insecure by default. Not nice.

    And the same is true for the next documented feature, Log::Log4perl::Config->allowed_code_ops(...). Quoting the documentation:

    By default, a value of '1' is assumed, which does a normal 'eval' without any restrictions.

    Insecure by default, you have to lock it down explicitly. Again, not nice.

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom