Sadly, TROOPERS 19 is already over. I had great fun meeting all of you, helping
you with your badge problems and seeing others hacking on their badges for
example to get custom images on there.
With this year’s badge we wanted to give you something you can reuse after the
conference, learn new things new build something on your own.
As promised in our talk Jeff and
I would like to give you a short introduction into the badge internals. Along
with this post we will release the source code for the badge firmware, the
provisioning server and the schematics for the PCB.
We’re happy to announce that some fine folks of ERNW will be present at the
upcoming ISH Conference.
The next generation IT security training facility for all industries and any
institution that manages complex infrastructure invites you to join the first
ISH Conference about threats, prevention and response in Information Security on
May 6th– 9th, 2019.
The event consists of two days of conference and two days of training with
insights and shared knowledge by world leading experts at the Information
Security Hub (ISH) Munich Airport.
Learn and discuss the newest threats and solutions with world-renowned experts
like Eugene Kaspersky, Adam Meyer, Adrian Nish and others.
When I got home last weekend after an awesome week at
WEareTROOPERS, my 5yr old asked me what
actually happened in Heidelberg…
I told him we were meeting with some people from all over the world to talk
about computer security, and he asked me if it was “to stop the bad guys, like
super-heroes?”. So I told him “yes, kind of…”, and he decided he would take his
new Troopers T-Shirt to school on Monday to show his classmates. Kids are truly
amazing… [<3 <3 <3]
We have the most amazing trainers this year lined up for Blackhoodie at
Troopers 2019. We have Thais,
Silvia, Lisa
and Ninon going to give workshops on various
interesting topics! Below are some of the workshop contents:
64-bit shellcoding and introduction to buffer overflow exploitation on Linux by Silvia Väli
64-bit shellcoding and introduction to buffer overflow exploitation on Linux is
a 3 hour workshop which is essentially divided into 3 parts:
Introduction to 64-bit architecture in order to get familiar with registers,
stack, calling conventions described in the Intel 64 (x86-64) architecture
manual and the most common assembly instructions and syscalls which we will
later use to write our shellcodes.
Shellcoding where we try different techniques to write the shellcode and of
course you gonna get to greet the shellcoding world with your own Hello
World shellcode in addition to reverse shell which we will use later on in
part 3
Introduction to buffer overflows, so you can put your newly received
know-how about stack into practise right away. Shellcode without being used
is a wasted shellcode! Part 3 ends with a buffer overflow challenge where
your goal is to use your reverse shellcode to get a connection back to your
machine.
We’re regularly asked to review IPv6 address plans from different organizations
and I’d like to share some reflections from such a process currently happening.
I’ve discussed a few aspects of IPv6 address planning before; those readers
interested please see
this post which
contains some references.
The organization in question is headquartered in Germany, has ~60K employees and
a number of subsidiaries in European countries. They belong to a “traditional
industry sector” (so they’re not an “Internet company”, even though they – as
the majority of large organizations right now – strive to be one in a few years
;-).
Starting a post, in 2019, with a mention of sth being “IPv4-only” somewhat hurts
;-), but here we go. Recently Manel Rodero
from Barcelona asked me the
following question on
Twitter:
In this post I’ll try to discuss some inherent aspects of that question and ofc
I’ll try to provide a response to it, too ;-).
Let’s first think about the main IPv6-related risks (= threats put into a
context of relevance) in an “environment [that] is only IPv4”. While some of
you might scratch your heads “what IPv6 threats could there be in an IPv4
setting?” I’m tempted to scratch my head: “what could be the reasons to run an
university network without IPv6 these days, or to use BIND?” (which I have a
strong opinion on, see here or
here). But I
disgress. More seriously the main reason for the question can be broken down to:
Last week I had the pleasure to attend
Offensivecon 2019 in Berlin. The conference was
organized very well, and I liked the familial atmosphere which allowed to meet
lots of different people. Thanks to the organizers, speakers and everyone else
involved for this conference! Andreas posted a
one tweet tldr of
the first day; fuzzing is still the way to go to find bugs, and mitigations make
exploitation harder. Here are some short summaries of the talks I enjoyed.
Some years ago Christopher wrote two posts
(2016,
2015)
about the IPv6-related characteristics of the WiFi network at Cisco Live
Europe. To somewhat continue this tradition and for mere technical interest I
had a look at some properties of this year’s setting.
There were two SSIDs of interest: a dual-stacked one (“CiscoLive2019”) and one
with v6-only plus NAT64 (“CL-NAT64”). For some background on the underlying
infrastructure components you might look at this
thread
by Nicolas Darchis from the NOC or
at this tweet
from Dominik Pickhardt. Some stats on
IPv6 usage at CLEUR can be
found here.
This year we had some excellent submissions for TelcoSecDay. Here are the first
four confirmed speakers who are going to talk about the below mentioned topics:
1. Telecom protocols revisited – Not just a signalling problem – by Fredrik Söderlund
A look at the design of the currently deployed signalling protocols for core
networks, both SS7 and Diameter (legacy and LTE). Peculiar quirks and how the
design has lead to the industry sometimes failing to adhere to its own
standards.
Back from Holidays, you started the year well motivated to make the world a
safer place.
However, sitting at your desk today you realize nothing really changed since
last year, and you are surfing the web, feeling a bit blue, trying to avoid that
pile of emails waiting for you and wondering how you could gain some
visibility on your domain in order to better defend it.
No worries, emails can wait a bit longer. All you need is some fresh air and
something cool to keep your defensive mind motivated for the year, and I might
have just what you need; so put on your shoes and let me take you on a 15 minute
Cypher walk with a cool blue dog…
