this post was submitted on 22 Jun 2023
215 points (99.1% liked)

Programming

18422 readers
403 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

I've heard people mention curl and imagemagick. Any others that you know about?

you are viewing a single comment's thread
view the rest of the comments
[–] BeePlusPlus@beehaw.org 49 points 2 years ago (3 children)

Log4j was a fun one to watch unfold everywhere when things went haywire

[–] axtualdave@lemmy.world 22 points 2 years ago (2 children)

The neat thing about the log4j thing was even a cursory explanation of the vulnerability made anyone with a passing familiarity with security say, "Why the fuck would that even be a feature?!"

[–] ColonelPanic@lemmy.ml 8 points 2 years ago (1 children)

Wait until you learn that PDFs support embedded Javascript.

[–] PowerSeries@lemmy.ca 2 points 2 years ago

????????? What the what now?

[–] Trusting@lemmy.sdf.org 7 points 2 years ago (3 children)
[–] JackbyDev@programming.dev 6 points 2 years ago

Basically it involved parsing JNDI stuff which involved grabbing remote code (but that was a niche feature of JNDI in the Dev's defense). Basically, you may think it is just something like variable substitution but can involve much crazier stuff

[–] subash@programming.dev 1 points 2 years ago
[–] OneDimensionPrinter@lemm.ee 8 points 2 years ago (3 children)

That was not a fun week to be a developer.

[–] boonhet@lemm.ee 12 points 2 years ago (1 children)

As a non-java company developer at the time, I think our biggest challenge was explaining to everyone that Log4j didn't affect us. It took a non-zero amount of effort because a lot of customers panicked. To be fair, it was also an industry where confidentiality is important.

[–] JackbyDev@programming.dev 5 points 2 years ago

Also a lot of people were pulling it transitively.

[–] BinaryEnthusiast@beehaw.org 3 points 2 years ago

Oh man. I missed it by like a month. I graduated with my bachelors in December, and started in January. I was hearing horror stories from my new coworkers about how people had to cancel vacations to get stuff patched asap

[–] argv_minus_one@beehaw.org 2 points 2 years ago (1 children)

It was if none of your code used log4j. I remember being very grateful that I had chosen java.util.logging and Logback for my Java logging needs.

[–] OneDimensionPrinter@lemm.ee 2 points 2 years ago

Lol, yeah for us we didn't own any of the code that used it but depended on server software made internally that did. At the time we managed our own hosts, so it was a long week of deployments.

[–] elrac@kbin.social 3 points 2 years ago (1 children)

That one was so annoying because you had to be using the log server to have any issues. If your network was locked down, the log server was disabled, or if you happened to be using a version that was from before the log server was added, then there were no issues. But clients just heard "log4j" and thought it was unsafe.