News for hackers. Stuff that matters.
Re:JavaScript Template Attacks by lioeters on Monday June 10, 2019 @09:18AM (#20146432)
Quick summary: an automated approach to browser fingerprinting, with two new side-channel attacks on browser engines, that reveals "the underlying operating system, CPU architecture, used privacy-enhancing plugins, as well as exact browser version".

Why it's called a JavaScript Template Attack: "A template is a matrix of properties (rows) for various environments (columns). All properties, e.g., browser properties, are retrieved through JavaScript."

Re:JavaScript Template Attacks by tantalor on Monday June 10, 2019 @09:28AM (#20146520)
> Why it's called...

I still don't get it, very weird name.

In JavaScript, "templates" are special strings that support interpolation: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

Re:JavaScript Template Attacks by lioeters on Monday June 10, 2019 @09:48AM (#20146669)
I agree the name is a bit confusing, I also immediately thought of template literals, wondering what kind of vulnerability it could have.
Re:JavaScript Template Attacks by kreetx on Monday June 10, 2019 @02:01PM (#20149151)
There's also a <template> html tag that one could relate the title to.
Re:JavaScript Template Attacks by thope on Monday June 10, 2019 @03:16PM (#20149826)
could be related to sidechannel template attack methodology:

https://wiki.newae.com/Template_Attacks

Re:JavaScript Template Attacks by tantalor on Monday June 10, 2019 @04:16PM (#20150377)
Yep it's actually mentioned somewhere in the paper:

Chari et al. [10] introduced template attacks as a strong form of side-channel attacks. They first collect side-channel traces from an attacker-controlled device, the so-called template. Then, they collect a single trace from an identical device processing an unknown secret. The unknown secret can then be recovered by comparing the trace to the recorded templates.

Re:JavaScript Template Attacks by mosdl on Monday June 10, 2019 @09:49AM (#20146682)
I don't see whats new here - comparing global object values has always been used to identify browsers and versions. Same with looking for bugs/quirks in JS engines.

New extension idea: adds random properties to window on each new page.

Re:JavaScript Template Attacks by antpls on Monday June 10, 2019 @11:06AM (#20147373)
I believe the new stuff is the exhaustive approach ("5796 different properties between Firefox and Chrome"), which is a bit scary actually.
Re:JavaScript Template Attacks by mosdl on Monday June 10, 2019 @12:11PM (#20148061)
Recursively walking a tree is new?
Re:JavaScript Template Attacks by hising on Monday June 10, 2019 @09:14AM (#20146403)
Link to Github-repo in slides https://github.com/IAIK/jstemplate
Re:JavaScript Template Attacks by XCSme on Monday June 10, 2019 @11:16AM (#20147458)
I watched the video presentation, what's the take-away from it? Yes, different environments have different properties, but we knew this since the first browsers appeared. Is there anything new? This does not lead to an unique fingerprint. Is it more about the automated system that detects the properties that change or just bringing awarness of the issue?