what is the log4shell vulnerability? (beginner - intermediate) anthony explains

Ғылым және технология

today we talk about the log4shell vulnerability, what is log4j, jdni, and more!
- make open source more sustainable: blog.filippo.io/professional-...
- consider sponsoring: github.com/sponsors/asottile
playlist: • anthony explains
==========
twitch: / anthonywritescode
dicsord: / discord
twitter: / codewithanthony
github: github.com/asottile
stream github: github.com/anthonywritescode
I won't ask for subscriptions / likes / comments in videos but it really helps the channel. If you have any suggestions or things you'd like to see please comment below!

Пікірлер: 23

  • @K.F-R
    @K.F-R2 жыл бұрын

    Terrific summary. Thanks. Completely agree that the problem is not the maintainers; rather the blind exploitation of their work, which is all too often completely taken for granted. After all, anyone could have spotted and fixed this - even someone being paid to do so.

  • @studiothree
    @studiothree2 жыл бұрын

    Thank you so much for this video, it really helped me get my head around what was going on. I appreciate you taking the time out of your day to speak about it!

  • @green727
    @green7272 жыл бұрын

    The explanation I've been looking for. Thank you so much!

  • @markjackson264
    @markjackson2642 жыл бұрын

    Hey Anthony, this was helpful. I just wanted to say thanks.

  • @Siddiskongen
    @Siddiskongen2 жыл бұрын

    Woonsan Ko will forever be known for Log4Shell....

  • @npiazzesi
    @npiazzesi2 жыл бұрын

    Stuff like this makes me always feel bad for big open source project mantainers and i completely agreenwith your final discourse. Too many parts rely and exploit the "open" part of open source. Grest video as always!

  • @ivanjacob_
    @ivanjacob_2 жыл бұрын

    Great explanation. Thank you!

  • @DavidDellsperger
    @DavidDellsperger2 жыл бұрын

    Great explanation!

  • @hielkovisser4753
    @hielkovisser47532 жыл бұрын

    Your great man the way you explain this is simply super

  • @erict8960
    @erict89602 жыл бұрын

    Thank you for the explanation, as someone who is younger and wasn't coding pre-2016 I was really confused about how such a feature even existed allowing code to be executed remotely and also as someone who hasn't worked on or maintained any open source projects understanding how such a feature could make it through.

  • @squirlmy

    @squirlmy

    2 жыл бұрын

    I think you're missing the point of Open Source. Remember Java itself wasn't Open Source, and it's very, very possible that lots of contemporary proprietary code contains such vulnerabilities, it's just undiscovered or unpublicized. Sorry to be defensive, but you seem to be implying FOSS is at fault in some way, when it's much more accurate to say this vulnerability could be examined and patched much more easily because it is Open Source. In fact, the possibility for it to have this video made about it is precisely because it is Open Source. Forget about understanding Apache vulnerabilities, you need to educate yourself about how FOSS works.

  • @erict8960

    @erict8960

    2 жыл бұрын

    @@squirlmy I'm not quite sure what you are arguing or defending. Nowhere did I say anything negative about open-source. I simply said that I gained a better understanding of how something could make it through to an open source project - because maintainers are working for free, they have limited time, and many projects are complex so some things slip through. You seem to be under the impression that I somehow am against open source? Yes, non-FOSS proprietary software can definitely, and does, have vulnerabilities like this. I never denied that nor stated that non-FOSS is better than FOSS. FOSS is better than non-FOSS in transparency and fixing vulnerabilities. I don't think there is blame to be placed on anyone here, not every situation must have a guilty party. I think you read my comment and assumed I was against FOSS and was blaming it. That's not the case

  • @AmrXcellent

    @AmrXcellent

    2 жыл бұрын

    @@erict8960 Talking from work experience, even paid jobs (high paid ones as well) suffer from the same thing, either too much work or out of touch leaders can merge/commit code that has vuln into the main tree. it happens all the time. You just hope that there is a security/QA team that can capture it before it gets released into the wild.

  • @johnlovell8299
    @johnlovell82992 жыл бұрын

    Thanks for the quick digestible coverage! I'm using the analogy of SQL injection for discussion purposes of this exploit since most devs are hyper aware of that exploit. Are the there other ways this vulnerability is being utilized that is not in the form of log injection?

  • @anthonywritescode

    @anthonywritescode

    2 жыл бұрын

    it can run arbitrary code, it is very different from a sql injection (which is usually around data extraction or validation bypass).

  • @typingcat
    @typingcat2 жыл бұрын

    What's the blue ball between the keyboards?

  • @anthonywritescode

    @anthonywritescode

    2 жыл бұрын

    it's a fidget spinner -- amzn.to/35PmPQr

  • @keenanhywood2951
    @keenanhywood29512 жыл бұрын

    Is JNDI the only Java API that makes log4shell possible?

  • @devinjones5972
    @devinjones59722 жыл бұрын

    Who’s going to patch the Rover?

  • @anthonywritescode

    @anthonywritescode

    2 жыл бұрын

    lol, I hope either (1) it doesn't accept arbitrary user input or (2) they can remote update it

  • @no_more_free_nicks
    @no_more_free_nicks2 жыл бұрын

    Lets the old people who use JNDI burn in hell! (I work with the JVM since 2002).

  • @SnoopyDoofie
    @SnoopyDoofie2 жыл бұрын

    And this folks is why you shouldn't use open source. There's no such thing as a free lunch. Welcome to the digital pandemic of 2021.

  • @anthonywritescode

    @anthonywritescode

    2 жыл бұрын

    I don't think that's the right conclusion -- there'd be no software without open source

Келесі