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
[–] 37 points 3 years ago (15 children)

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

  • source
  • hideshow 15 child comments
  • [–] 17 points 3 years ago (6 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?!"

  • source
  • parent
  • hideshow 6 child comments
  • [–] 6 points 3 years ago (3 children)
  • [–] 5 points 3 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

  • source
  • parent
  • [–] 7 points 3 years ago (5 children)

    That was not a fun week to be a developer.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 8 points 3 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 3 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

  • source
  • parent
  • [–] 1 point 3 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 3 years ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment