_markel___ Profile Banner
Mark Ermolov Profile
Mark Ermolov

@_markel___

Followers
12K
Following
2K
Statuses
2K

I research security of Intel platforms. I don't work for Intel

Москва, Россия
Joined September 2014
Don't wanna be here? Send us removal request.
@_markel___
Mark Ermolov
5 years
Finally, the casket is opened: we (+@h0t_max and @_Dmit) have extracted Intel x86 microcode! One more Intel "top secret" information gets revealed...
Tweet media one
Tweet media two
19
385
965
@_markel___
Mark Ermolov
2 days
They fired the pcode programmer... Who will fix the bugs now?
Tweet media one
1
3
38
@_markel___
Mark Ermolov
5 days
Most likely the PoC was obtained brute forcing mutable bits of a patch for which it was known for certain that it makes changes to the rdrand instruction...
0
0
10
@_markel___
Mark Ermolov
8 days
@_MatteoRizzo @misc0110 Great work, congratulations! Waiting for AMD ucode ROM dump/disassembler...
0
1
15
@_markel___
Mark Ermolov
8 days
RT @taviso: This was a huge research project -- at least some details are partially released today! 😩
0
39
0
@_markel___
Mark Ermolov
8 days
@taviso Patch for a bug in the patch loading ucode in MSROM? That's unfixable in my opinion...
2
0
8
@_markel___
Mark Ermolov
16 days
RT @wipawel: An excellent undocumented instruction chase story. Must have been a lot of fun.
0
4
0
@_markel___
Mark Ermolov
20 days
RT @taviso: welp, it looks like an OEM leaked the patch for "AMD Microcode Signature Verification Vulnerability" 🔥 The patch is not in linu…
0
59
0
@_markel___
Mark Ermolov
1 month
MOWs are sent to NDA-ed customers (having privileged Intel RDC access) and describe changes in Pre-Production HW/FW/Docs of selected products. You can find many useful info in MOWs such as hw bug fixes, all issued microcode patch revisions, existing collateral doc numbers...
0
0
6
@_markel___
Mark Ermolov
1 month
The king is dead! Long live the King!
Tweet media one
2
3
33
@_markel___
Mark Ermolov
2 months
RT @a13xp0p0v: Slides for my talk at @h2hconference 2024: Diving into Linux kernel security 🤿 I described how to learn this complex area…
0
82
0
@_markel___
Mark Ermolov
2 months
RT @InstLatX64: #Intel opened a "Trusted Computing Base Recovery of Intel Trusted Execution Environments" page: htt…
0
4
0
@_markel___
Mark Ermolov
3 months
A big step forward in reverse engineering of Intel p-unit firmware (pcode): managed to match the debug trace message IDs in the pcode with the message IDs from the .xml files of Intel System Trace utilities. Huh, many things become clearer...
Tweet media one
Tweet media two
Tweet media three
Tweet media four
0
18
148
@_markel___
Mark Ermolov
5 months
@a66ot I don't do a drama, I just do a research 😀
1
0
6
@_markel___
Mark Ermolov
5 months
RT @EduardKovacs: Intel has shared some clarifications on claims made by a researcher regarding the hacking of its SGX security technology.…
0
6
0
@_markel___
Mark Ermolov
5 months
0
0
2
@_markel___
Mark Ermolov
5 months
@sbellem To overcome the issue, yes, they should remove all known Root Provisioning Keys of GLK/R from their RAS databases
1
0
2
@_markel___
Mark Ermolov
5 months
@Analytic_ETH @socrates1024 @PratyushRT @kobigurk That's CSME Anti Rollback Prevention. Most vendors don't enable it
1
0
1