Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
If I posted about everything I repair, there'd be a gazillion threads/posts about it all....I may post about something unusual now and then...but otherwise bore people with my kooky boredom builds.
Some serious security bug in INTEL CPUs?? Since Westmere possibly
Collapse
X
-
Re: Some serious security bug in INtel CPUs?? Since Westmere possibly
This is not remotely exploitable, you need a way to put code on a victims system.
For example Javascript in a browser from a shady website.
Or malicious code via some other entry point like e-mail or such.
None of this should be running on a fileserver so that wont even need to be patched technically, because walled off properly it could never be exploited.
All you had to do to get exploited, with the 2003 and 2004 incidents, was to hop on the internet without a firewall!
You could get exploited within seconds on 56K, IIRC!Last edited by RJARRRPCGP; 01-21-2018, 11:43 AM.Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
As long as you can find components or repair the old ones the customer will keep using the machines...
Of course I don't post very frequently about these repairs, but some I do post about.
https://www.badcaps.net/forum/showthread.php?t=39747
https://www.badcaps.net/forum/showthread.php?t=37091
http://www.jonnyguru.com/forums/show...78&postcount=5Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
Have not actually had such in my hands, but I judge so from the volume of Pentium 4 (478) CPUs which I still resell. You get it pratically for free so even few bucks is nice sale (when the only work is cleaning it and making the advertisement).Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
I repair a lot of that stuff too... Seems like the CNC guys loved Soyo P3 & P4 boards, with ISA of course.Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
Curious.George: what kind of Sun HW are we talking about? Anyways, it is not only about the SW, which is huge price today, it is also the whole HW ecosystem. Also remeber that big corporations have totaly different price of electricity, that's one of the last things which actually impact anything if we are talking about some industrial machinery.Leave a comment:
-
Re: Some serious security bug in INtel CPUs?? Since Westmere possibly
For example Javascript in a browser from a shady website.
Or malicious code via some other entry point like e-mail or such.
None of this should be running on a fileserver so that wont even need to be patched technically, because walled off properly it could never be exploited.
If the fileserver runs in a Virtual Machine with many other systems I'd be very afraid of exploitation though!Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
[If you don't upgrade for a few decades, the prospect of upgrading is closer to sheer terror than anything else!]Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
I thought these CPU bugs were gone the way of the dodo.
I remember the "KAP" processor which was supposed to be a SPARC clone, but had so many bugs fixed in the OS/software that it can't run SunOS anymore...
And around the same time was the more or less flawless(?) 486? What 486 bugs were there?Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
IIRC, for the first gen Phenoms, the solution is to replace your processor with a model having the suffix "50"... (And thus, for example, "8750" is in the clear, and "8700" is the faulty one!)Last edited by RJARRRPCGP; 01-20-2018, 04:25 PM.Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
If you have a P120 or newer, it should not have the fdiv bug.
It may have the F00F bug but it can be worked around and thus not recalled.
---
As per post 140, I have experimentally verified my Core2 Quad (and also Core2 Duo) that predate all of the Intel-listed processors are at least affected by Spectre.
I do wonder how hard it is to find the process table if all kernel addresses are random with ASLR within physical memory... Searching may be very time consuming, and the slower machines are even worse: I would think that the older machines (PPro to P3) are even more difficult to exploit beyond their inherent slowness because they have poor time measurement capability and lack state resetting capability within userspace, albeit they are still vulnerable. Chips starting with the P4 and Pentium-M and anything newer start to gain these things and thus are more dangerous.
---
I would suggest that any machine that is subject to new, arbitrary code frequently to be most vulnerable (think: new apps, scripts, javascript, flash, ...). In this respect, other than the fact servers are not monitored, as long as servers run the same code over and over again and only download trusted code, they are safe. In any case, at least for Linux, the Meltdown fix (KPTI) is available for 64-bit and soon available for 32-bit x86; so after that patch, it'll be as safe as AMD boxes that may be affected by Spectre.Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
CorrectLeave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
intel does not produce bioses. (except for it's own boards)
they produce microcode and modules - updates are regularly put out.
it's upto the motherboard maker to bother compiling an update or not.Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
^
I know corporations still using pentium4-era stuff....I still get things that old in for repair by businesses.Leave a comment:
-
Re: Some serious security bug in INtel CPUs?? Since Westmere possibly
The performance bug is actually *really* interesting, and also fucking terrible because there's literally *no way* to patch it on any processor without completing changing how CPUs work.
Effectively, processors perform "speculative execution" and "out of order execution" where upon hitting a branch instruction in code, may decide to execute instructions ahead of time, before the result of the branch is known. This is a performance advantage, because in many cases the branch could take many cycles to evaluate (if it needs to read from arbitrary memory, then up to 300 cycles on a modern i7). So the processor executes these instructions and then if it finds out later that the branch was wrong, it rolls back the results. This is completely transparent to the user: incorrect data is never visible or committed.
Spectre seems to work by exploiting speculative execution, which processors have had for about 15 years. You can write code that will trick the branch prediction logic into executing a block of malicious code. The code will run speculatively - but the catch is, it's not possible for the CPU to prevent reads to protected areas of memory, like other processes or the OS kernel. The CPU sorts this out *after* the speculative execution has finished, and it can check which areas are OK and which are no go (it must do this check afterwards because it can't be sure of the memory map yet). Now, normally this is not a problem because the malicious code cannot "output" anything - it remains transparent as the results never get committed because the addresses are found to be prohibited. But, by inserting timing-dependent code into the speculative execution block, you can "leak" data out of the execution path. You could make it take 10 cycles to process a "1" and 2 cycles to process a "0", then time many hundreds of executions.
The example Google provided can read out any memory at 11KB/s, which isn't fast, but it's more than fast enough to exploit a system within ~10 minutes. You only need to find the Windows/Linux kernel process table, then you know the addresses of each application and can go to town on reading passwords, security keys, etc.
It's a complete bombshell, and I'm frankly surprised INTC and other companies aren't feeling a stronger hit.
People that cannot afford to replace their systems will need some workaround. Perhaps using an AMD machine as a file server for their unprotected Intel boxes.
How is this accomplished and would it work?Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
So when I get such old Pentium, it is likely it still has the bug? There is always somebody who does not get the replacement. I think that all systems check for the affected CPUs and in case they find them, they apply patch, no? At least Linux kernell does anyway.Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
That incident required physical hardware replacement, you were required to dump your CPU chips per-se!
IIRC, Intel said that the Pentium 133s and higher, don't have the hardware bug...
The mid-1990s Intel incident, was a lot worse than "Meltdown" and "Spectre".
IIRC, late-1990s' Windows NT 4.0, had a work around for such Pentiums detected, but then the Pentiums will act like OC'ed 486 SXes, LOL.Last edited by RJARRRPCGP; 01-20-2018, 12:53 PM.Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
Westmere is older than 5....but yea, typical Intel. I guess the world will explode, I'm not gutting systems over this. This whole thing totally reeks planned obsolescence scam to begin with.Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
It's just Intel being assholes and not making Microcode updates available for CPU's older than 5 years.
They did the same with WiFi chipsets and the KRACK attack: no new drivers for WiFi chipsets older than 5 years.Leave a comment:
-
Re: Some serious security bug in INTEL CPUs?? Since Westmere possibly
Leave a comment:
Related Topics
Collapse
-
Hi guys!
I have a Dell Optiplex 760 USFF (Ultra-Small Form-Factor).
It currently only supports Dual-Core CPUs and will halt with an error message, when a QuadCore is installed.
I have seen people running QuadCores in these machines, but the BIOS needs to be modded.
Since I have not found the modded BIOS to download anywhere, I am asking you guys for help:
Could you please add support for QuadCore CPUs (in my case the Core2Quad Q9550) to the BIOS?
I have attached the Dump of my machine.
S/N: SRW2K4J
Reg Model: DCTR...-
Channel: BIOS & Schematic Requests!
09-27-2024, 02:43 AM -
-
by ducky29Hello. I mostly do small electronics and tv repairs. I am confident with small bga chips but I never was successful with removing large chips especially cpus. Is it possible to remove them just using a preheater and hot air gun or I need something more advanced like a bga machine with temperature profiles, cooling fans, etc etc.
Any suggestion on aliexpress/ebay are welcomed. I am on a tight budget, max I can do is about 200$. Please anyone with more experience can give me some suggestions?
Thanks in advance.09-23-2024, 03:56 PM -
by ugamazingI have been working to develop a consistent and reliable method/workflow for removing, re-balling, and replacing CPUs on various MacBook Pro models (2015-2020).
I have done OK so far, but there's one detail I need to sort out. I'm hoping someone much more experienced than myself may be able to shed some light:
I am noticing the pulled CPUs (to be re-balled) come off fine, and they "look" fine as well, immediately when I pull them. However, within a few minutes, after cooling, the CPU chips develop a very, very slight curve/bend. It's SO SLIGHT, maybe a 1-2%... -
by bigbearkAccordng to the ASUS website, if you apply BIOS 5001 you can use Socket AM3 CPUs on the M2N-E motherboard.
I have two of these boards that are working. The CPU support info on the ASUS site says you can use ATHLON II X2 CPUs, Athlons II X3, and even Athlon II X4 CPUs.
These CPUs seem to be readily available at reasonable prices. There are some that consume as little as 45 watts.
The notes say "Due to Bios ROM size limitation remove LAN PXE ROM and change Crashfree3 to Crashfree".
I assume these are options in the BIOS setup you can... -
by Alfiehhey Im very new to repairing electronics with capacitors as well as using a multimeter so I need so help/guidance fixing this issue
recently I was handed a family members old NAD C320BEE that they had in their loft for storage for a few years but when powered on it went into power safety mode due to a problem on the protection circuit somewhere before it went into storage I was told it worked fine I found lots of people online talking about how the capasitors are known to be pretty bad in this model and can cause this issue the only problem being I don't have much experience sorting...-
Channel: Troubleshooting Audio Equipment
-
- Loading...
- No more items.
Leave a comment: