Massive Intel Breach – 20GB of Confidential Design Information (CPU IPs & Documents) Leaked

Intel

Intel has suffered quite a sizeable data breach leaking over 20GB of confidential microarchitecture and engineering information through a Swiss IT consultant. The information along with several documents which include confidential information of existing and upcoming CPU IPs have been leaked within the 'Intel Exconfidential Lake Platform Release'.

'Intel Ex-Confidential Lake' 20GB Folder Leaks Out - Intellectual Property Released to the Public

A folder containing Intel's intellectual data was shared on Twitter at some point, and while it's unclear exactly what has escaped confidential status, the following list comes directly from the individual in regards to what has been leaked.

  • Intel ME Bringup guides + (flash) tooling + samples for various platforms
  • Kabylake (Purley Platform) BIOS Reference Code and Sample Code + Initialization code (some of it as exported git repos with full history)
  • Intel CEFDK (Consumer Electronics Firmware Development Kit (Bootloader stuff)) SOURCES
  • Silicon / FSP source code packages for various platforms
  • Various Intel Development and Debugging Tools
  • Simics Simulation for Rocket Lake S and potentially other platforms
  • Various roadmaps and other documents
  • Binaries for Camera drivers Intel made for SpaceX
  • Schematics, Docs, Tools + Firmware for the unreleased Tiger Lake platform
  • (very horrible) Kabylake FDK training videos
  • Intel Trace Hub + decoder files for various Intel ME versions
  • Elkhart Lake Silicon Reference and Platform Sample Code
  • Some Verilog stuff for various Xeon Platforms, unsure what it is exactly.
  • Debug BIOS/TXE builds for various Platforms
  • Bootguard SDK (encrypted zip)
  • Intel Snowridge / Snowfish Process Simulator ADK
  • Various schematics
  • Intel Marketing Material Templates (InDesign)
  • Lots of other things

In a statement to Tom's Hardware, Intel claims the leaked information comes primarily from Intel's Resource & Design Center, but this is refuted by the leaker.

We are investigating this situation. The information appears to come from the Intel Resource and Design Center, which hosts information for use by our customers, partners and other external parties who have registered for access. We believe an individual with access downloaded and shared this data.

Most of the leaked files are claimed to have been obtained earlier this year. The files are reported to be of classified status, under NDA, or under Intel Restricted Secret, and therefore none of these files have been published or released to the public. If you've been lucky enough to obtain the reported 20GB folder, the leaker claims encrypted files are password protected by either 'Intel123' or 'intel123'. The leaker also claims future information will 'have even juicier and classified stuff.'

Intel's claim that the leak originates from its Resource & Design Center appears to be false. It's hard to believe Intel would share any bits or pieces of information on the Intel Management Engine (ME) considering it is a closely guarded secret and highly controversial, let alone 'Binaries for Camera drivers Intel made for SpaceX' as that crosses into the intellectual property of another organization, even to individuals with access to the Resource & Design Center.

Last but certainly not least, the leaker mentions Intel building 'backdoors' into its source code. Call me a conspiracy theorist, but could this be the enabling factor of Meltdown, Spectre, and the various other Intel processor security vulnerabilities? If these backdoors are pre-planted, there is some shady work going on over at Intel, especially considering the leaked information is reported to be marked with NDA to 'Centerem Information Co. Ltd., a Chinese company established and existing under the laws of the People's Republic of China,' of which could have also been hacked.

The post Massive Intel Breach – 20GB of Confidential Design Information (CPU IPs & Documents) Leaked by Alexander Buck appeared first on Wccftech.



Refference- https://wccftech.com

Post a Comment

0 Comments