[ 3 / biz / cgl / ck / diy / fa / g / ic / jp / lit / sci / tg / vr / vt ] [ index / top / reports / report a bug ] [ 4plebs / archived.moe / rbt ]

Due to resource constraints, /g/ and /tg/ will no longer be archived or available. Other archivers continue to archive these boards.Become a Patron!

/g/ - Technology

View post   

[ Toggle deleted replies ]
File: 226 KB, 1024x768, 051184.jpg [View same] [iqdb] [saucenao] [google] [report]
60168584 No.60168584 [Reply] [Original] [archived.moe] [rbt]

Intel Active Management Technology, Intel Small Business Technology, and Intel Standard Manageability are subject to a hole allowing an unprivileged attacker to gain control of the management features for these products. The issue was made public today via INTEL-SA-00075.

For those with AMT enabled on their systems, it can affect supported processors going back to 2008 when AMT6 debuted -- thus the vulnerability covers from Nehalem to Kabylake CPUs.




>> No.60168604


>> No.60168745

i'm too retarded to know if this effects me or not
i've been using my i3-6100 skylake cpu for around a year completely out of the box no changes at all
does this affect me?

>> No.60168757


Step 1: Determine if you have an Intel® AMT, Intel® SBA, or Intel® ISM capable system: https://communities.intel.com/docs/DOC-5693. If you determine that you do not have an Intel® AMT, Intel® SBA, or Intel® ISM capable system then no further action is required.

Step 2: Utilize the Detection Guide to assess if your system has the impacted firmware: https://downloadcenter.intel.com/download/26755. If you do have a version in the “Resolved Firmware” column no further action is required to secure your system from this vulnerability.

fuck offfff you're just lazy

>> No.60168774
File: 232 KB, 800x1200, Promotion+Ads+of+SNSD+at+Intel+exhibition+in+Taiwan+%5B11.02.13%5D+%285%29.jpg [View same] [iqdb] [saucenao] [google] [report]

>The short version is that every Intel platform with AMT, ISM, and SBT from Nehalem in 2008 to Kaby Lake in 2017 has a remotely exploitable security hole in the ME (Management Engine) not CPU firmware. If this isn’t scary enough news, even if your machine doesn’t have SMT, ISM, or SBT provisioned, it is still vulnerable, just not over the network. For the moment. From what SemiAccurate gathers, there is literally no Intel box made in the last 9+ years that isn’t at risk. This is somewhere between nightmarish and apocalyptic.


Is is a Intel Box?

Was it made any time during the last 9 years?

>> No.60168781

eh whatever
honestly i don't care i'm gonna continue browsing porn now

>> No.60168925

SNSD aged like milk.

>> No.60168933

I wouldn't take advantage of their vulnerabilities if you know what i mean

>> No.60168950


i just checked my cpu specs and it doesn't have that gay vPro stuff so i'm p sure i'm ok

>> No.60169122
File: 1.03 MB, 1000x1500, 1492346432398.jpg [View same] [iqdb] [saucenao] [google] [report]


You did not just try to say that about princess Taeyeon, did you?


>> No.60169163

> tfw amd


>> No.60169187
File: 44 KB, 500x333, w_500.jpg [View same] [iqdb] [saucenao] [google] [report]


>The Intel® SCS – System Discovery utility is a standalone executable (SCSDiscovery.exe)

>Massive security vulnerability
>Only way to check is an .exe

>> No.60169460

(((Intel))) = botnet, confirmed.

>> No.60169567
File: 79 KB, 444x560, happy.png [View same] [iqdb] [saucenao] [google] [report]

tfw you can still escape the otherwise inevitable botnet because you have the option to just switch to an older PC when it starts getting really bad

>> No.60169947

Options are now 10+ year old Intel laptops or AMD laptops. Ryzen Mobile needs to come out.

>> No.60170042


In an effort to make Intel® AMT easier to use, to support cross platform and over the Internet usages, we are building a new version of the MDTK that is fully written in JavaScript. There are many advantages in doing this, but above all, it just makes a lot of sense. With HTML5 being very capable, it's a lot easier for administrators to use web applications that interact with Intel AMT within a browser, making the local installation of tools a thing of the past in some cases.

Below, we have a new version of Manageability Commander that is fully written in JavaScript and uses a new WSMAN stack, redirection stack along with remote desktop and remote terminal libraries. You can use this new version as-is or can download the source code and samples to build your own web based Intel AMT tools. Also look at the overview presentation and screen shots.

>> No.60170476


I've always known that the shitty programs in the processor were buggy and vulnerable, but now we have factual confirmation.


>> No.60170520


>> No.60170847

>tfw Penryn

>> No.60170914
File: 99 KB, 1280x720, 1492831980248.jpg [View same] [iqdb] [saucenao] [google] [report]


>> No.60170939

Coorect link for mitigation guide is

>> No.60170943
File: 127 KB, 600x1266, just.jpg [View same] [iqdb] [saucenao] [google] [report]

You mean all alone?

>> No.60170944

is that morning musume?

seriously I don't even

>Was it made any time during the last 9 years?
jesus christ intel


like that's a shock

>> No.60170948


>> No.60170952
File: 162 KB, 633x900, 1489103005792.png [View same] [iqdb] [saucenao] [google] [report]

Please delet dis

>> No.60171043

The interesting question now is will AyyMD ride this and make PSP more security-friendly?

>> No.60171189
File: 20 KB, 620x349, 1493664956366.jpg [View same] [iqdb] [saucenao] [google] [report]

Stop buying AMD.

>> No.60171243


>> No.60171282

Does this mean Pentium 4 is safe to use?

>> No.60171295

regarding the OP vulnerability: yes. Many 775 chipsets are fine too.

Intel ME is an old tech and affects 775 socket: https://en.wikipedia.org/wiki/Intel_AMT_versions

>> No.60171307

Stop supporting thieves and conmen.

>> No.60171332

>This vulnerability does not exist on Intel-based consumer PCs.


>> No.60171350

Are the vulnerabilities that exist in old chipsets of greater or lesser concern than AMT?

>> No.60171372

Check it out yourself:

I don't know whether you will find everything there.

>> No.60171373

>This vulnerability does not exist on Intel-based consumer PCs.

>> No.60171380

What is "consumer PC"?

>> No.60171398

Literally anything that isn't a Xeon.

>> No.60171404


Look up your processor on Google and click the ark.intel link. Look for "Intel® vPro™ Technoloy"

If no, you're fine. If yes, worry. Testing on the 2500K, 3770K, and 6700K and none of them have it.

>> No.60171405


>> No.60171406

>the vulnerability covers from Nehalem to Kabylake CPUs.

>Kaby Lake Xeons

>> No.60171410

That's a lot of reading, anon. What's the short answer?

>> No.60171432

>read it for me

>> No.60171446

>tfw rolling a Q9550

>> No.60171455

Haha I knew sticking on my old Duos and Celeron would pay off!

>> No.60171699

It isn't the only way to check it, if you bother to read the PDF.

>> No.60171728

>look up my i7-4770 on ark.intel
>vPro: Yes
>run scsdiscovery
I don't know what to believe anymore.

>> No.60171923

Here a disturbing question:
Does AMD CPUs have similar problems that we simply don't know about?

>> No.60171925

The CPU supports vPro, but motherboard isn't. You'll need a special business chipset which enables IPMI-like capabilities.
I think Thinkpads support vPro, by the way.

>> No.60171971

The Register calls this a RED ALERT!

> These insecure management features have been available in various, but not all, Intel chipsets for nearly a decade, starting with the Nehalem Core i7 in 2008, all the way up to this year's Kaby Lake Core parts. Crucially, the vulnerability lies at the very heart of a machine's silicon, out of sight of the operating system, its applications and any antivirus.


From what I gather you need both a motherboard and a CPU with vPro support for this to be exploited.

The funny thing is that you apparently need to get the _motherboard_ vendor to give you a firmware patch. With all the motherboards that has support for this produced the last decade.. there's going to be a lot of unpatched motherboards out there.

I mean.. anyone really expect firmware patches for 4-5 year old motherboards?

>> No.60171973

>backdoor feature can be used as a backdoor

And this is a shocker why exactly?

>> No.60171984

Article literally says

>This vulnerability does not exist on Intel-based consumer PCs.

>> No.60172010

Can't the feature just be disabled in the processor?

>> No.60172034

No because it is a gov backdoor.

>> No.60172055

It's most likely that any motherboard vendor that is not supporting a board anymore probably doesn't have vPro enabled on that board.

>> No.60172071

Definitely a serious issue for corporations but it seems that most of the fear mongering about it around these parts ended up just that, fear mongering with nothing for us to worry about because we don't buy motherboards with the support.

>> No.60172076

What exactly could someone do with the vulnerability?

What exactly would it give to a virus that it can't do already?

>> No.60172131

Complete control of everything on your system remotely while hidden from every piece of software running on your system.

>> No.60172306

Direct memory access from the firmware.
No software can protect you.

>> No.60172321

With virus you have to actually infect computer before it can work. This is a remote vulnerability. This is something that lets, among other things, to plant a virus into the computer.

>> No.60172327

>What exactly could someone do with the vulnerability?
Anything, seriously

>> No.60172340

>An extreme vulnerability that remained undetected for almost 10 years
Lmao Intel

>> No.60172388

Hmmm it's almost like it was a deliberately installed backdoor.

>> No.60172406

But a firmware update can.

>> No.60172422

Yeah, I don't know how that will be distributed and delivered to millions of critical servers though...

>> No.60173894

Steamroller, Excavator, and Ryzen all have a similar thing called the Platform Security Processor. AMD has considered open sourcing it for use with coreboot though. Which will probably allow disabling it on at least Ryzen.

>> No.60173951

It's been known for years, Intel refused to patch it. The fact they're coming out now in a panic means malware finally exploited it.

>> No.60173980

I am fucked, I have an X220 and my desktop PC uses an i5 4460.

It's sad. SAD.

>> No.60174193

Intel security is compromised big time
Vulnerability level similar to Heartbleed (OpenSSL) in 2014
Intel has just patched a security vulnerability that affects all of its desktop and notebook platforms from Nehalem in 2008 to Kaby Lake in 2017, with a higher degree of vulnerability for users on Intel vPro systems.
The vulnerability, which our friend Charlie at SemiAccurate has been trying to get the company to fix for nearly five years now, affects every Intel platform with AMT, ISM and SBT. The list includes every desktop and notebook platform Intel has released since first-generation Core series Nehalem processors in 2008 through the 7th-gen Kaby Lake processors currently on the market.
In Intel's May 1st security advisory, any machine can allow an attacker to “gain control of the manageability features provided by these products” either locally or remotely. On the local end, Intel says “an unprivileged network attacker could gain system privileges to provisioned manageability
Even if a machine does have AMT, ISM or SBT provisioned, it is still classified as being locally vulnerable to attack but not remotely vulnerable.

>> No.60174261


>> No.60174274
File: 333 KB, 480x480, ring0.webm [View same] [iqdb] [saucenao] [google] [report]

Is this still the ring0 vulnerability that was detected in 2008-2009-ish?

>> No.60174479

>The fact they're coming out now in a panic means malware finally exploited it.

or you know, they have a fuckton of patched ICs to sell
maybe you can even get 10% off if you bring your old cpu

>not riding the intc since $19
as if you don't even want to get rich

>> No.60174487

8350 isnt 10 years old and still works well. Also ppc still isnt botnet. And in the worst case scenario we can always use cellbe

>> No.60174610

I bought all intel cpus for my family and me. All of them were made during the last 9 years.
What do I have to do to be safe? As simple as possible please.

>> No.60174630

>What do I have to do to be safe? As simple as possible please.
you have to research. how did you not know about this anyway?

>> No.60174646

>in worst case scanario we can use a arch that isn't produced at all, that's also just an in-order PPC core with some really slow vector units hamfistedly attached.
I'd rather be vulnerable than use Cell.

>> No.60174672
File: 986 KB, 640x798, 10753751_476664265870387_208944310_n.webm [View same] [iqdb] [saucenao] [google] [report]

At least Intel has good taste in girls

>> No.60174686

For this to be exploited you need both CPU and motherboard that has this functionality. If you bought consumer motherboards and computers then you should not worry. If you have thinkpad or business dell series then you are in trouble, and you must wait for patches from those manufacturers.

>> No.60174700

it was a joke. But none the less it can still be used

>> No.60174732

ARM based home computers will be our salvation.

>> No.60174785

>ARM based home computers will be our salvation.
fucking hell do you even know what automated remote management is?

>> No.60174799

They're super locked down and have security processing too...

Our best hope is nVidia trying on x86 again.
Intel will probably say no again (although, right now, they might just say yes to prevent the lawsuit) but nVidia could possibly win in a suit now due to Intel's shit security potentially harming US National Security.

>> No.60174811

>Our best hope is nVidia trying on x86 again.
l i s c e n c i n g

>> No.60174824

They will be our salvation in a way that we will have a lot of different producers to choose from. It will be easier to get one without botnet.

>> No.60174886

no it wont, you have no idea what youre talking about. its a standard feature now days, and having multiple competing architechtures is always a nightmare for devfelopement. were better off having the x86 licence be free and having competing companies producing the same chip. of course we can all see why that wont happen.

>> No.60174968

I'm >>60174799

I think it might actually happen - this itself might be the catalyst.
USA needs x86 for many aspects in government and beyond.
US Gov needs at least 2 suppliers under normal circumstances
US Gov *MUST* buy US designed CPUs
x86 Licensing has been a thorn in USGOV's side
A massive security issue might suspend sales from single vendor until their products can be revalidated.

It's high time for nVidia to try on x86 again - the courts might rule in their favor in the current climate, which would set a massive precedent, potentially underlying a massive change in x86 licensing.

Fuck ARM, if the cards are played right here, we could free x86 from its current chains...

>> No.60175172

>claim security bulletin
>the whole world installs malware v2

Has anyone actually seen the exploit? Where is that ball-licker Kerbs when you need him

>> No.60175212

>A massive security issue might suspend sales from single vendor until their products can be revalidated.
no it wont, the us gov wants RM to stay in every cpu for obvious reasons. theres no laws being broken so theres no incentive for the courts to rule in nvidias favour if they ever do decide to waste money on swift failure.

>> No.60175303

Parts of USGOV but they're not all the same nor are they allied to each other, except when they need to present a unified front.
x86 is a thorn in all depts sides but can't be ditched.

>> No.60175325
File: 355 KB, 512x512, 󠀁󠀁󠀁󠀁😒.png [View same] [iqdb] [saucenao] [google] [report]

Stallman is an idiot and a faggot queer communist. Terry was right

>> No.60175375

can they take their shirts off?

>> No.60175480
File: 5 KB, 188x236, images.jpg [View same] [iqdb] [saucenao] [google] [report]

>Security software written in Javascript and HTML5

>> No.60175508
File: 25 KB, 495x364, 1491874379734.jpg [View same] [iqdb] [saucenao] [google] [report]

>mfw there will be recall

>> No.60175587

she aged the worst

>> No.60175622

Stallman is always right.

>> No.60175895

>having multiple competing architechtures is always a nightmare for devfelopement.
Hey, think of it this way, more processors to support means more needed workforce meaning more jobs and MAYBE cheaper hardware.

>> No.60175978

What the fuck I love Intel now

>> No.60175987

Nvidia is going to have a fun time getting the license for AMD_64

>> No.60176005
File: 319 KB, 930x1836, test-fullpage.png [View same] [iqdb] [saucenao] [google] [report]

>How do I know if I have it enabled?
>Yeah this is way more annoying than it should be. First of all, does your system even support AMT? AMT requires a few things:

>1) A supported CPU
>2) A supported chipset
>3) Supported network hardware
>4) The ME firmware to contain the AMT firmware

>Merely having a "vPRO" CPU and chipset isn't sufficient - your system vendor also needs to have licensed the AMT code. Under Linux, if lspci doesn't show a communication controller with "MEI" or "HECI" in the description, AMT isn't running and you're safe. If it does show an MEI controller, that still doesn't mean you're vulnerable - AMT may still not be provisioned. If you reboot you should see a brief firmware splash mentioning the ME. Hitting ctrl+p at this point should get you into a menu which should let you disable AMT.

>> No.60176054
File: 5 KB, 631x38, 20170502.png [View same] [iqdb] [saucenao] [google] [report]


>> No.60176074

Anyone know where to find a list of '08-'09 chipsets that don't have ME?

>> No.60176238

Not really, AMD is pretty open to licensing.
It won't necessarily be cheap, but it'd be available.

>> No.60176337

Maybe they'll learn their lesson and start releasing CPUs without the ME, or at least a firmware update for the ME and BIOS that allows users to shut it off. I'm sure businesses aren't too happy.

Anyways, why are freetards always right?

>> No.60176497

Same fag that asked before here.. So I got a rampage v extreme and it had some AMT buñlshit in the options but I think everything was disabled. Should I check someting else besides that and disable it? The other vulnerale features will also show up in the bios as ISBT etc right? Or should i pay attention to some other stuff?
The MEI firmware cant be downgraded, at leadt on the RVE. If the other intel cpus are on non high end motherboards with no AMT options in the bios I souldnt be worried right? Or should I be even more worried because I habe no way to disable it?

Someone got hypervisor on my network a few months ago and I think this might be ehat they used to get in so im extremely paranoid with this. Thanks everyone,

>> No.60176606

And what do you do with all your data collected during all these years?

>> No.60176670

Why is there no outrage? No corporate lawsuits against intel? Just some articles and 2 threads on 4chan and that is it. There was bigger outcry when amd put an add into their drivers.

>> No.60176812

because no one's dumbed it down in a way that normies could understand it yet

>> No.60176831

Well, unless you're running a Mac. Intel has confirmed for a decade that vPro and AMT aren't on the chips they put in Macs.

>> No.60176836


>> No.60176907

lol, that doesn't make any sense. isn't Intel what's inside my computer? the people who made my computer hacked it? crazy conspiracy theories much lmao


>> No.60176911

Who didn't see this coming?

>> No.60176966

They still include a management engine and a vulnerable EFI.

>> No.60177007


good thing us mac users are too smart for them. ;). *sips starbucks*

>> No.60177036

>i7 930
>i7 3610QM
>i7 4930K

All negative. And my X5450 is Core 2-based.

A sigh of relief.

>> No.60177094


>sigh of relief
>false sense of security
>you are actually still compromised by the always-on second cpu you can't even control

>> No.60177311


I can't wait when I get off from this ride

>> No.60177376

I have a T61 with T7300 CPU.
How fucked am I?

>> No.60177396

>This vulnerability does not exist on Intel-based consumer PCs.

/g/ can't read it seems but then again, all AYYMDPOOJEETS can't read in the first place

>> No.60177436

>damage control
You fucking moron the ME is on every chip

>> No.60177447
File: 180 KB, 277x268, eheh...heh...ehh....png [View same] [iqdb] [saucenao] [google] [report]

A nervous laugh.

>> No.60177479

This is patently false, it exists but not necessarily through the network

>> No.60177619

"consumer PCs" being PCs designed and targeted specifically at consumers, not the PCs actually used by consumers. Plenty of business-targeted laptops with it enabled that are also sold to consumers.

>> No.60177708

Hey retards, just google the processor name and find the intel ark link. ctrl+f for vPro and if it says "No", then you don't have anything to worry about.
If it says "yes", then it's time to throw out dad's old work laptop and get a new one.
The patch is already released, you just need to update Intel Manageability Firmware to build 3xxx. If you work for a company and have the ability to do this yourself, then do it. If not, contact IT or don't worry about it because it's not your problem and if your IT department doesn't know, then they deserve to be fucked by it.

>> No.60177928

Everybody was worried of issues like this one when hardware manufacturers started putting useless over engineered bullshit in their hardware and firmware.
This particular intel technology had basically a (hopefully involuntary) hardware backdoor in it since 2008 and the problem was fixed only now. This is worrisome especially considering this is not going to be the last accident with superfluous hardware and firmware features.

>> No.60178119

I'm not saying it isn't an important issue on a larger scale, I just hate to see half of the posts read, "THE WORLD IS BURNING". This is just another event that people have to react to, not the apocalypse.

>> No.60178288

i5 2500k here, how fucked ?

>> No.60178293

does this affect atoms at all?

>> No.60178315

>Implying anyone of you neckbeard jobless neets have vpro processors in their system

>> No.60178334

Well, retard if there is no particular section for vPro, how can I know that there is no vPro when not even intel is unable to tell if there is one?
>what is /tpg/

>> No.60178353

vpro processors are sold on business systems. Don't worry, you don't have one.

>> No.60178365


Literally only prebuilts have this problem.
Thats how you tell.

>> No.60178410

I have X220 and T61.
I can't find information on T7300, but X220 is fucked.

>> No.60178427

>x220 and t61
Enjoy your special snowflake problems

>> No.60178449

It's okay, the useful life of your consumer electronic is already approaching the end.

>> No.60178455


we fixed now?

>> No.60178471

>check processor
>ctrl+f vPro
*sigh of relief*

>> No.60178479

nah hooking the ME is not fixed by this I think

>> No.60178495
File: 964 KB, 397x658, just do ti.gif [View same] [iqdb] [saucenao] [google] [report]

Only death can know peace from this hell.

I'm just waiting if they manage to get fusion nuclear powerplant working because then Helium will be cheap.

>> No.60178955

Any companies except Purism Librem working on open/secure hardware?

Thinking routers, e-readers, phones or cheap laptops.

>> No.60179477

>The fact they're coming out now in a panic means malware finally exploited it.
Or this backdoor was about to come to light anyway in the near future as it's in the CIA's shit that Wikileaks is realeasing piece by piece

>> No.60179532

Intel was a mistake

>> No.60179560

Basically you are only seen this on vpro CPUs, like latitudes and thinkpads

>> No.60179600

Only a handful of skus have vpro, mostly laptops, and all are oem integrated. If you have vpro your hardware have a vpro sticker.

>> No.60179612

I think a company dedicated to security could still theoretically secure their system against Intel ME, simply by creating a system which wraps the NIC, accessible through the BIOS menu. You can block ports at the hardware level, and Intel ME won't be able to do shit about it.

>> No.60179743

It depends on what you define as consumer. Some shit OEM walmart laptop wouldn't have the issue, but some consumer PCs definitely will. AMT isn't restricted to Xeons.

>> No.60179750

Yuri and Yoona are the best, just wanted to say that.

>> No.60180175

>I think Thinkpads support vPro, by the way.

>> No.60180260

>Kaby Lake Xeons
My Xeon E3-1240 v6 would like a word with you

>> No.60180292

You cannot equate a similar feature to having same implementation vulnerabilities. This is absurd.

>> No.60180373

thank you based i7 2630qm

>> No.60180390

>Intel Confirms Vulnerability In Intel AMT/ME
Why though?

>> No.60180417
File: 19 KB, 500x323, 1391442963178.jpg [View same] [iqdb] [saucenao] [google] [report]

>tfw libreboot

>> No.60180488
File: 29 KB, 438x396, hehe.jpg [View same] [iqdb] [saucenao] [google] [report]

>tfw Q6600

>> No.60180540



>> No.60180669
File: 25 KB, 895x375, intel-mei.jpg [View same] [iqdb] [saucenao] [google] [report]


>> No.60180679

The CVE is: 2017-5689
Help me guys, the description says that the expoit works only on provisioned management engine. Does this means that I need to enable (provision) it? If it's unprovisioned then im good?

>> No.60180692

>ITT: linuxfags panic about "security"

>> No.60180964

Press the button to get to the BIOS and turn AMT off. We also told you to install trannyboot.

>> No.60182436
File: 494 KB, 373x213, 2e8ae174141682774588669433_700wa_0.gif [View same] [iqdb] [saucenao] [google] [report]

I know ...

>> No.60182510

I think you're good, if I'm not mistaken it was produced around 2007 and the vulnerability only affects cpus produced from 2008 and up

>> No.60182534

Stallman only speaks of general truths. It's just convenient to ignore him

>> No.60182553


>> No.60182765

Yeah, I panic for nothing. I wasn't able to rationally think and check the architecture name and then check from this list

Now my next problem would be X220 with vPro. It would be quite embarrassing to leave my X220 airtight (no internet connection) and using T61 for my future studies.

>> No.60182861

AMT can be provisioned by an unprivileged local attacker. So if an attacker can run code on your system (by tricking you, or exploiting some other vulnerability) then they can gain ring -3 privileges with this exploit.

>> No.60182979

Well yeah, he knows his shit. It was only a matter in time before closed source network-enabled firmware running on negative rings was exploited. It's the perfect vulnerability.

>> No.60183582

You should check first from the command line if it is enabled with "lspci | grep MEI" unfortunately, my EliteBook has it

>> No.60184940
File: 164 KB, 2100x1505, IMG_9850.jpg [View same] [iqdb] [saucenao] [google] [report]

Posting from my IBM X40 Thinkpad, I don't have this problem.


>> No.60185109

Just Pajeet things...

>> No.60185784

What if I don't HAVE an IT department? Guess you didn't think of that, genius.

>> No.60186104

That's great, we can all just wildly dig in scrapyards for CPUs made prior to 2008 and we'll be fine.

Feels a bit like going backwards, doesn't it.

>> No.60186210

This whole thing really sucks because I wanted to set up AMT at work. On the bright side, almost nobody here is going to be affected.

You're only affected if AMT is provisioned or if you have Intel's LMS service installed and running. The former doesn't apply to you. It's not provisioned on your personal hardware. You'd know if it was because it's a pain in the ass to do. Maybe you have LMS installed for some reason if you've got a bunch of vendor installed shit-ware still on your machine, but it's very easy to remove. Just open a command prompt and run "sc config LMS start=disabled" or "sc delete LMS"

>> No.60186254
File: 501 KB, 739x931, tmp_11546-1493322772356-1089550412.png [View same] [iqdb] [saucenao] [google] [report]

Sometimes you have to take one step back, to make two steps forward Anon-kun.

>> No.60186267

>This backdoor only works if you have it enabled.


>> No.60186300

Yes. The remote exploit only works if you have AMT provisioned.

>> No.60187191

RIP every single thinkpad still worth using.

>> No.60187478

The *60 and *200 series can all have ME disabled. The X220 received a firmware update in October of 2016, so Lenovo might still patch this.

>> No.60187492

What if you set it to "Permanently Disabled" in the BIOS? It's possible on some platforms.

>> No.60188126

I stopped reading his stuff after he got all high on himself and perceived a retaliatory ddos attack on his site as an attack on press freedom. Has his recent stuff been better?

>> No.60188151
File: 36 KB, 560x590, Bp64bAy.jpg [View same] [iqdb] [saucenao] [google] [report]

Burch is beyond JUST

>> No.60188480


Doesn't this only effect idiots who purchased a OEM Desktop (excluding server administration here). And people who installed every driver and feature possible on their mobo disk? Like if you built your desktop, you'd have to go out of your way to install this software, even if running intel chip of the time and a board that supports it.

>> No.60189432

>(hopefully involuntary)
Anon, I...

>> No.60189509

You don't HAVE to utilize this new information and get a secure computer anon. If you're lazy or stupid you can just ignore the problem.

>> No.60189899

>Systems vulnurable:
>Intel® manageability SKU firmware versions >6.x.x.x
>11.6.x.x with a build value less than 3000
what do? Just wait for gigabyte to update my h87 chipset or what?

>> No.60190018

Just use your emergency pre-ME era stinkpad until they update the firmware anon.

>> No.60190106

>Government backdoor can also be used by non-government
Hmmm... Who would have thought this would happen?

>> No.60190155
File: 853 KB, 3840x2160, 140607 가족e스포츠페스티벌 AOA - 흔들려 혜정 직캠.mp4_20170503_125600.732.jpg [View same] [iqdb] [saucenao] [google] [report]


>> No.60190238

Nah, this one is ring -3

>> No.60190544
File: 84 KB, 653x726, 1491958654249.png [View same] [iqdb] [saucenao] [google] [report]

Wait for Cannonlake.

>> No.60190582
File: 28 KB, 354x286, 1489911666347.png [View same] [iqdb] [saucenao] [google] [report]

Link to qt old song from SNSD (Made possible by Intel™)

>> No.60190739

>There is an escalation of privilege vulnerability in Intel® Active Management Technology (AMT), Intel® Standard Manageability (ISM), and Intel® Small Business Technology versions firmware versions 6.x, 7.x, 8.x 9.x, 10.x, 11.0, 11.5, and 11.6 that can allow an unprivileged attacker to gain control of the manageability features provided by these products. This vulnerability does not exist on Intel-based consumer PCs.

>This vulnerability does not exist on Intel-based consumer PCs.


>> No.60190760

explain this, cocksuckers

>> No.60190784
File: 37 KB, 1280x720, 456546873.jpg [View same] [iqdb] [saucenao] [google] [report]

jews gonna jew
what did you expect of jewtel?

>> No.60191564

worse even, but for some reason people still give him stuff. Only guy on the net that people still co-operate with for some reason. Everyone else just self-publishes or leaks to some tiny website and then conglomerate webcorp picks it up.

>> No.60192988


>> No.60192994

No way!! A hardware backdoor can be used for malicious purposes??? Who could've possibly imagined such a thing???

>> No.60193092

So, what happens if you just don't install MEI drivers?

>> No.60193977
File: 1.23 MB, 912x905, 1491056584900.png [View same] [iqdb] [saucenao] [google] [report]

>Failed to get data from the MEI interface. (0xc000283d). Failed to connect to the Intel(R) Management Engine Interface PTHI client. (0xc000001c).
>This system does not have Intel(R) AMT (or it is disabled in the Intel MEBX, or the correct drivers are not installed or enabled, or the current user does not have permissions to the drivers)

>> No.60195249

Stop gookposting.

>> No.60196333

Those look fast and expensive.

>> No.60198311

You do realize even if you don't have AMT enabled, the ME is running and likely has more vulnerabilities?

>> No.60200548
File: 60 KB, 550x314, sales-training-to-be-the-damsel-in-distress.jpg [View same] [iqdb] [saucenao] [google] [report]



>> No.60200591


why do chinks bleach there hair like that

>> No.60200595

My X40 is still good anon. It even has OpenGL graphics.

>> No.60200616
File: 29 KB, 509x355, iyzVdAv.jpg [View same] [iqdb] [saucenao] [google] [report]

Why do they chisel off their jawbones or bury perfectly good cabbage and dead shrimp in the yard?

Nobody knows anon.

>> No.60200632
File: 24 KB, 320x350, Screen Shot 2017-05-03 at 4.16.30 PM.png [View same] [iqdb] [saucenao] [google] [report]

How long since this guy's had succ?

>> No.60200849

Dunno what that is but this is basically a ring -3 or so vulnerability so probably not.

>> No.60201745

So are cpus that directly don't have vpro support affected? If vpro is 'collection of computer hardware technologies, including Hyperthreading, Turbo Boost 3.0, VT-x, VT-d, Trusted Execution Technology (TXT), and Intel Active Management Technology (AMT).' Does it mean having any of those puts me at risk? Or am I retarded? Also, does it need a mobo that supports this, or is it just enough to have the cpu?

>> No.60204655
File: 68 KB, 600x300, jennifer-aniston-middle-finger.jpg [View same] [iqdb] [saucenao] [google] [report]

>>>60168584 (OP)
>>tfw libreboot
Fuck I had to scroll way to far for this.

>> No.60204694

This particular exploit is just ME. But look into AMT because that is the same scary shit

Name (leave empty)
Comment (leave empty)
Password [?]Password used for file deletion.