- Joined
- Apr 16, 2010
- Messages
- 3,600 (0.67/day)
- Location
- Portugal
System Name | LenovoⓇ ThinkPad™ T430 |
---|---|
Processor | IntelⓇ Core™ i5-3210M processor (2 cores, 2.50GHz, 3MB cache), Intel Turbo Boost™ 2.0 (3.10GHz), HT™ |
Motherboard | Lenovo 2344 (Mobile Intel QM77 Express Chipset) |
Cooling | Single-pipe heatsink + Delta fan |
Memory | 2x 8GB KingstonⓇ HyperX™ Impact 2133MHz DDR3L SO-DIMM |
Video Card(s) | Intel HD Graphics™ 4000 (GPU clk: 1100MHz, vRAM clk: 1066MHz) |
Storage | SamsungⓇ 860 EVO mSATA (250GB) + 850 EVO (500GB) SATA |
Display(s) | 14.0" (355mm) HD (1366x768) color, anti-glare, LED backlight, 200 nits, 16:9 aspect ratio, 300:1 co |
Case | ThinkPad Roll Cage (one-piece magnesium frame) |
Audio Device(s) | HD Audio, RealtekⓇ ALC3202 codec, DolbyⓇ Advanced Audio™ v2 / stereo speakers, 1W x 2 |
Power Supply | ThinkPad 65W AC Adapter + ThinkPad Battery 70++ (9-cell) |
Mouse | TrackPointⓇ pointing device + UltraNav™, wide touchpad below keyboard + ThinkLight™ |
Keyboard | 6-row, 84-key, ThinkVantage button, spill-resistant, multimedia Fn keys, LED backlight (PT Layout) |
Software | MicrosoftⓇ WindowsⓇ 10 x86-64 (22H2) |
If proved true, the usual applies.Subjectively speaking, compared to Meltdown attack page, this one has waaaay too many AMD logos. Without reading the text, one might actually mistake it for an ad! Count me up holding a pitchfork if Intel turned out to have a hand in this.
Objectively speaking, smear campaign or no, a vulnerability is a vulnerability. I'm personally quite illiterate on this matter so I'll defer judgement until "for dummies-"style security expert blog posts and articles start popping up.
Common sense running programs and visiting the internet, make sure you have backups (cold ones preferably), patch as soon as possible.
Only if it's embedded in firmware, but to reach that far, so much needs to be compromised to begin with...When it can survive a reinstall it's still a big issue. If these flaws are confirmed they are fairly signifigant.
As I said earlier, 2018 is going to be a rough year for processor security...