Datasets:
Devilishcode
/
hacking

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.99k
|=---=[ Personal
Other Interests: Electronics! Woodworking. Making things. Creating Tech.
Philosophy: If it has a solution, it’s not a problem. And if it
doesn’t, why worry at all? Carpe Diem, totally, during the
night when I’m statistically more productive.
Zines: Conferences are ephemeral. Zines are forever, and the
articles are usually well thought. A blog is fine, but
without an editor pushing you to get it done, the quality
degrades over time.
|=---=[ Quotes
Yes: Backticks, please, best quotes ever.
And maybe:
“I want room service!” - standing on a pile of trash.
Though the written story is better than the movie.
|=---=[ Closing Thoughts
CALL $+4
RET
POP EBX
==Phrack Inc.==
Volume 0x10, Issue 0x48, Phile #0x03 of 0x12
|=-----------------------------------------------------------------------=|
|=---------------------=[ L I N E N O I S E ]=---------------------------=|
|=-----------------------------------------------------------------------=|
|=------------------------=[ Phrack Staff ]=-----------------------------=|
|=-----------------------------------------------------------------------=|
Linenoise is a collection of artifacts that do not fit elsewhere.
Short papers, corrections, brain dumps, late papers, etc..... :))
Contents
1 - Barbie Sparkles -- Barbie
2 - Another use for the EICAR test file -- Peter Ferrie
3 - Hacker: Apotheosis of the Marginalized -- Kolloid
4 - A Hacker's Introduction To CHERI -- xcellerator
5 - High-Performance Network Scanning With AF_XDP -- c3l3si4n
6 - MMIO in the Middle -- b1ack0wl
7 - Shell Your Way to Network Mastery -- Gabriel & Thomas
8 - Breaking ToaruOS -- NOT / Firzen,
Binary Gecko
|=-----------------------------------------------------------------------=|
|=-------------------=[ 1 - Barbie Sparkles ]=-------------------=|
|=-----------------------------------------------------------------------=|
|=----------------------------=[ barbie ]=-------------------------------=|
|=--------------------=[ phrack@barbieauglend.re ]=----------------------=|
|=-----------------------------------------------------------------------=|
--[ 0 - Introduction
For a long time, data stored in microarchitectural buffer-like structures'
behaviors were believed to be strictly internal to the CPU and protected by
architectural mechanisms built into modern CPUs, many of them lacking
detailed public documentation. Since 2018 following Microarchitectural Data
Sampling (MDS) attacks [1] the security community discovered that the
contents of such buffers might be inferred or even, under the right
circumstances, directly leaked using e.g., faulting load instruction or in
the shadow of transiently executed flows. These techniques might allow
attackers to bypass such architectural mechanisms and other hardware
mitigations, e.g. buffer clearing or overwriting.
Lots of such microarchitectural buffers have been documented publicly by
now, as well as mitigations have been deployed on newer hardware with this
new threat model in place by most CPU vendors. Unfortunately, we show that
not all CPU vendors have adopted this new threat vector into their threat
model, and some newer architectures are being released having such
dangerous behaviors documented.
In this article, we show that it is possible to observe stale data from
previously evicted cache entries from an undocumented microarchitectural
buffer, which we are calling eviction buffer. More specifically, AMD Zen 4
platforms might enable a malicious process to observe data that is
previously evicted from a victim process, even if the same victim process
has been previously terminated.
Moreover, unlike most of prior data inference attacks from
microarchitectural buffers, this behavior has been documented in the
official “AMD Zen4 Microarchitecture Documentation” and AMD does not
consider a security concern.