RT @fcbunn: It seems Xcode has the Log4j vulnerability 🙃
RT @snyksec: 🚨 Overnight, @TheASF disclosed that #Log4j version 2.16 is also vulnerable by way of a DOS attack with the impact being a full…
RT @AndyBurnhamGM: #IsThisOK?
RT @brwngrldev: Learn about @Meetup journey to adopting Kotlin Multiplatform Mobile => https://medium.com/making-meetup/adopting-kotlin-multiplatform-mobile-kmm-at-meetup-326b2b0a4186
#kmm #androiddev #iosdev
RT @debugagent: Coding tests in an interview are redundant.
We spend more time debugging and reading code than coding in a normal day to…
This is a really interesting post from about the numbers around the #log4shell vulnerability. More interesting perhaps are the numbers about the projects that copied the code from the #Log4j project - https://blog.sonatype.com/why-did-log4shell-set-the-internet-on-fire
RT @qos_ch: In response to a vulnerability report LOGBACK-1591, we have released logback version 1.2.8.
See http://logback.qos.ch/news.html for d…
RT @sjmaple: Here’s a #Log4Shell Remediation cheat sheet I wrote with my @snyksec colleague @byte89
Plenty of options of how to find and…
RT @cr00ster: Less than an hour now before we kick off! #infosec #appsec
RT @MaartenvSmeden: This is why programming is an acquired skill
Hi, I’m Lee 👋. Senior Software Engineer at WireMock, Snyk Ambassador, Hacker of code. Appsec enthusiast. Runs Brighton Kotlin & Brighton JUG