Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. The claim that Mythos found its "flagship" BSD bug because the upstream Kerberos bug/patch from 2007 is in the training set is very interesting.

The claim that Mythos found its "flagship" BSD bug because the upstream Kerberos bug/patch from 2007 is in the training set is very interesting.

Scheduled Pinned Locked Moved Uncategorized
4 Posts 3 Posters 0 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • lapt0r@infosec.exchangeL This user is from outside of this forum
    lapt0r@infosec.exchangeL This user is from outside of this forum
    lapt0r@infosec.exchange
    wrote last edited by
    #1

    The claim that Mythos found its "flagship" BSD bug because the upstream Kerberos bug/patch from 2007 is in the training set is very interesting. It significantly weakens the novel discovery claim, but makes me wonder about the implications for how transformers evaluate input weights and whether this could be extracted and leveraged as a variant hunting technique.

    Or maybe you could just straight grep for the vulnerable code block from every patch ever and see what falls out. That may also be embarrassingly effective.

    demha@comp.lain.laD acdha@code4lib.socialA 2 Replies Last reply
    0
    • lapt0r@infosec.exchangeL lapt0r@infosec.exchange

      The claim that Mythos found its "flagship" BSD bug because the upstream Kerberos bug/patch from 2007 is in the training set is very interesting. It significantly weakens the novel discovery claim, but makes me wonder about the implications for how transformers evaluate input weights and whether this could be extracted and leveraged as a variant hunting technique.

      Or maybe you could just straight grep for the vulnerable code block from every patch ever and see what falls out. That may also be embarrassingly effective.

      demha@comp.lain.laD This user is from outside of this forum
      demha@comp.lain.laD This user is from outside of this forum
      demha@comp.lain.la
      wrote last edited by
      #2
      @lapt0r LLMs are great librarians but the mythos thing is a larp by amodei. still LLMs are gigantic security threat only because of slopware.
      1 Reply Last reply
      0
      • lapt0r@infosec.exchangeL lapt0r@infosec.exchange

        The claim that Mythos found its "flagship" BSD bug because the upstream Kerberos bug/patch from 2007 is in the training set is very interesting. It significantly weakens the novel discovery claim, but makes me wonder about the implications for how transformers evaluate input weights and whether this could be extracted and leveraged as a variant hunting technique.

        Or maybe you could just straight grep for the vulnerable code block from every patch ever and see what falls out. That may also be embarrassingly effective.

        acdha@code4lib.socialA This user is from outside of this forum
        acdha@code4lib.socialA This user is from outside of this forum
        acdha@code4lib.social
        wrote last edited by
        #3

        @cigitalgem @lapt0r the back to back Linux LPEs might be coloring my view but I think there’s a lot of potential in that idea of looking for the same pattern elsewhere, especially for the major projects which people often copy-paste from or where package management was historically hard enough to encourage copying code you weren’t going to carefully track upstream (C, PHP, etc.)

        lapt0r@infosec.exchangeL 1 Reply Last reply
        0
        • acdha@code4lib.socialA acdha@code4lib.social

          @cigitalgem @lapt0r the back to back Linux LPEs might be coloring my view but I think there’s a lot of potential in that idea of looking for the same pattern elsewhere, especially for the major projects which people often copy-paste from or where package management was historically hard enough to encourage copying code you weren’t going to carefully track upstream (C, PHP, etc.)

          lapt0r@infosec.exchangeL This user is from outside of this forum
          lapt0r@infosec.exchangeL This user is from outside of this forum
          lapt0r@infosec.exchange
          wrote last edited by
          #4

          @acdha @cigitalgem variant hunting is a time honored security research tradition and tools for doing it at scale have never been better (and will continue to improve)

          1 Reply Last reply
          1
          0
          • R relay@relay.infosec.exchange shared this topic
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups