If you can modify the config, you can modify the rest of the application.
True in Perl, Python, Javascript etc., not necessary in Java, C++, etc. - or at least harder.
It boils down to proper access permissions and running the application always with least privileges.
The core of Log4Shell is the unexpected or little known behaviour of the library to contact remote services.
Usually, I would expect from a configuration file to hold static read only data, not fractions of code that could be
executed - and that's also unexpected or little known Log::Log4perl behaviour.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
