News for hackers. Stuff that matters.
Re:New Log4j2 vulnerability by formerly_proven on Tuesday December 28, 2021 @05:29PM (#29719067)
Eh, that sounds like it's not a vulnerability at all. Most app server configuration files allow you to load and run arbitrary code.
Re:New Log4j2 vulnerability by phoronixrly on Tuesday December 28, 2021 @05:37PM (#29719153)
Yeah, maybe should be mentioned in the title to save people from PTSD over the holidays...
Re:New Log4j2 vulnerability by xaner4 on Tuesday December 28, 2021 @05:44PM (#29719214)
If I could have have changed the title I would have added something to make it give less PTSD
Re:New Log4j2 vulnerability by frogger8 on Tuesday December 28, 2021 @06:07PM (#29719427)
Re:New Log4j2 vulnerability by johnisgood on Tuesday December 28, 2021 @06:03PM (#29719391)
> Most app server configuration files allow you to load and run arbitrary code

I do not understand this. Configuration files allow you to load and run arbitrary code? Is this actually a thing? What are they using for configuration files?! Tcl?

Re:New Log4j2 vulnerability by filleokus on Tuesday December 28, 2021 @06:23PM (#29719590)
If I remember correctly e.g Django and Flask uses plain old python-files for configs. Don’t know if it’s common in the Node landscape but probably?

I don’t know how common it is to specify paths to/file name for DLL’s in config to load at runtime for C#, but probably not totally unheard of? And if you can edit the config, maybe you can place a DLL somewhere as well…?

(But at the some time if you can edit the config, maybe you can just replace/patch the main binary in the first place…)

Re:New Log4j2 vulnerability by teh_klev on Tuesday December 28, 2021 @06:39PM (#29719703)
You can configure ASP.NET to load HTTP Handlers and Modules for use in the request/response pipeline via the web.config file (from the file system, not over HTTP).

But if your attacker has gotten so far as to be able to tamper with these config files then it's probably game-over already.

Re:New Log4j2 vulnerability by capableweb on Tuesday December 28, 2021 @06:41PM (#29719720)
> Don’t know if it’s common in the Node landscape but probably?

Webpack is (arguably) one of the most common tools in the nodejs/browser ecosystem, and it has a regular JS file as it's config file (usually named `webpack.config.js`).

Re:New Log4j2 vulnerability by johnisgood on Tuesday December 28, 2021 @06:54PM (#29719819)
I am still stuck at using INI/JSON/TOML for configuration files. :D
Re:New Log4j2 vulnerability by capableweb on Wednesday December 29, 2021 @04:32AM (#29723283)
Just remember that just because you're using .ini/.json/.toml files doesn't mean there isn't any way of executing code from changing their values, it's up to whatever is using the files if there is any way of executing code via them.

One example is package.json. It's a JSON file, yeah, and normally doesn't contain any code. But one of the fields is `scripts` which can contain a object with a key like `preinstall` (and more) that runs those as shell commands at different lifecycle of using `npm`.

So just because you're using those languages/syntaxes, doesn't mean there isn't any way of executing code via them.

Re:New Log4j2 vulnerability by johnisgood on Wednesday December 29, 2021 @10:54AM (#29725911)
That is fairs and true. :) Thanks!
Re:New Log4j2 vulnerability by blacksqr on Wednesday December 29, 2021 @01:10PM (#29727682)
>What are they using for configuration files?! Tcl?

This would be preferable, since Tcl allows you to configure safe interpreters that can deny use of any specified set of commands, including those that give access to files and network services.

https://www.tcl.tk/man/tcl8.6/TclCmd/safe.html

Re:New Log4j2 vulnerability by rst on Tuesday December 28, 2021 @06:22PM (#29719579)
In a typical installation of something like Apache Tomcat, there will be config files that tell the server what code to load and run. If you can modify those config files...