He is a security researcher in Google’s Project Zero. He has been involved with
computer hardware and software security for over 10 years looking at a range of
different platforms and applications. With a great interest in logical
vulnerabilities he has numerous disclosures in a wide range of products from web
browsers to virtual machine breakouts as well as being a Pwn2Own and Microsoft
Mitigation Bypass bounty winner. He has spoken at a number of security
conferences including Black Hat USA, CanSecWest, Bluehat, HITB, and Infiltrate.
Troopers is (unfortunately) over. It was a blast (but I may be biased ;-))!
After things have settled, I want to take the opportunity to reflect my thoughts
and impressions on the IPv6-only WiFi we had deployed during the conference. To
make sure that everybody is on the same page let’s start at the beginning.
In the last couple of years we had provided Dual-Stack connectivity on the main
“Troopers” SSID but also had an additional IPv6-only SSID. This year we decided
to spice things up and made the “Troopers“ SSID IPv6-only (with NAT64) while
providing Dual-Stack connectivity on the “Legacy“ SSID. We wanted to get a
feeling how many clients and applications can work properly in an IPv6-only
environment. We intentionally didn’t announce it vastly beforehand, hoping that
attendees would just connect to the main SSID without noticing anything. We were
aware that some applications might expose issues but, as I said , we wanted to
get a feeling to which degree problems actually occured.
I’ve recently found some sort of classic web vulnerabilities in the Google
Search Appliance (GSA) and as they are now fixed [0][1][2], I’d like to
share them with you.
First of all, some infrastructure details about the GSA itself. The GSA is used
by companies to apply the Google search algorithms to their internal documents
without publishing them to cloud providers. To accomplish this task, the GSA
provides multiple interfaces including a search interface, an administrative
interface and multiple interfaces to index the organization’s data.
Real men used to wear pink pagers, but that’s the past and recently it was time
for Troopers 16. Meaning: Real Troopers wear awesome Badges! And, from the
feedback we got, they did!
Troopers might be over, but the era of the TR16 Badge is seemingly just
beginning. As such, here’s a quick insight into the badge!
To start, this is the first of (at least) three blogposts covering the badge. As
we’re currently in the middle of stripping and cleaning our source code
repository, this post now will not cover the firmware. The stripping is not
about hiding something, but as we used an Open Source
RTOS our repo
currently contains modules, which are for completely other architectures.
In addition we needed a few workarounds while getting the badge up and running
for the conference, following our own hacking sessions, there will be a
dedicated post concerned with hardware modifications and hacks which can be
performed.
only a few seconds left! As a short reminder, there is a GSM network running on
Troopers 2016. It should be available in the whole building. To attend the
network you need to
Get a SIM Card @Troopers_Desk
Put it in your phone
Start the phone
That’s it!
You can always dial *#100# to get your phone number. All further
information (and a phonebook) you’ll find on gsm.troopers.de, but here again a
brief summary:
This is a guest post from Joris van de Vis @jvis,
on his upcoming Troopers
talk.
Additional credits go to: Robin Vleeschhouwer, and Fred van de Langenberg.
As
presented at Troopers
this year, ERP-SEC research has uncovered a set of potential default accounts
related to the use of SAP Solution Manager. These default accounts might pose a
big risk to your SAP supported business as some of them have wide
authorisations. It is therefore important to check if they exist in your
landscape and change the default passwords.
I gave a presentation on Cloud Security, Compliance & Trust the other day. The
basic message was to look beyond the Cloud buzzword and see the actual
technologies which are used, understand which security principles still apply
and which need to be re-thought, giving a rough direction about regulatory
compliance in Cloud environments (which of course is non-binding, as I’m not a
lawyer), and the importance of trust evaluations (especially) when it comes to
Cloud services.
this week I gave a presentation together with
Florian Barth from
Stocard on Docker, DevOps/Microservices, and Security
— a topic and collaboration that I will definitely cover in even more detail in
the future!
Only a few days left until Troopers! I’d like to use this chance to publish the
final agenda of
TelcoSecDay 2016.
We will start around 8:30am and will finish at about 6:15pm. After this, we will
have a shared dinner in the historic center of Heidelberg. The exact location
will be announced during the TSD.
Same as last year, we will
have a GSM based telephony network running at Troopers 2016. The network will be
a closed network, which means it only can be used with Troopers SIM cards and
between Troopers attendees only. You can use the network for
doing Voice Calls
send Short Messages (SMS)
have Internet Access
submit Challenge Tokens (see below)
In contrast to last year, you will need a Troopers SIM card to attend the
network with your cellphone. The SIM cards will be handed out at the
registration desk; if you have questions you always can contact me or Kevin
Redon (thanks again for assisting us).
