Semiconductor Fabricator TMSC annouced that they were hit with a virus that multiple pieces of their production operation in Taiwan. TMSC alleges the virus entered their systems as they were installing software for a new tool. TMSC's full announcement:
Issued by: TSMC
Issued on: 2018/08/05
Hsinchu, Taiwan, R.O.C., Aug 5, 2018 – TSMC today provided an update on the Company’s computer virus outbreak on the evening of August 3, which affected a number of computer systems and fab tools in Taiwan. The degree of infection varied by fab. TSMC contained the problem and found a solution. As of 14:00 Taiwan time, about 80% of the company’s impacted tools have been recovered, and the Company expects full recovery on August 6.
TSMC expects this incident to cause shipment delays and additional costs. We estimate the impact to third quarter revenue to be about three percent, and impact to gross margin to be about one percentage point. The Company is confident shipments delayed in third quarter will be recovered in the fourth quarter 2018, and maintains its forecast of high single-digit revenue growth for 2018 in U.S. dollars given on July 19, 2018.
Most of TSMC’s customers have been notified of this event, and the Company is working closely with customers on their wafer delivery schedule. The details will be communicated with each customer individually over the next few days.
This virus outbreak occurred due to misoperation during the software installation process for a new tool, which caused a virus to spread once the tool was connected to the Company’s computer network. Data integrity and confidential information was not compromised. TSMC has taken actions to close this security gap and further strengthen security measures.
Today disclosure of two plaintext leaking behaviors in email clients handling OpenPGP and S/MIME encrypted messages has been released (archived). The vulnerability affecting S/MIME is baked into the S/MIME standard and may only be mitigated by abandoning S/MIME, no other mitigation is possible. Meanwhile the plaintext leaking behavior affecting OpenPGP encrypted emails requires certain common but very stupid behavior on the part of an email client and the user allowing the email client to be involved in decrypting the message.
The attack in OpenPGP encrypted email involves the message being molested on the wire in such a way the plaintext metadata surrounding the cyphertext is modified to engage your typical email client's HTML rendering engine. If the email client is allowed to be involved in decrypting the cyphertext as is common with various client "plugins", the email client can "phone home" the plaintext after decryption to the message's molester according to the spurious instructions delivered to the HTML rendering engine. The mitigation for this vulnerability is hygiene and not allowing your email client to be involved in cryptographic operations beyond sending and recieving cyphertext blobs encrypted and decrypted elsewhere.
Intel has killed its Android and iOS "Intel Remote Keyboard" app used to manage embeded computers in their line of Internet of Shit products (archived). The move was prompted by the discovery of three vulnerabilities allowing keystroke injection and arbitrary code execution. Rather than patch these vulnerabilties and the others likely to be found, Intel simply killed the app leaving their customers to find other remote management solutions.
Bram Cohen's (WOT: nonperson) venture "Bittorrent Inc." has let the full 90 day window for a remote execution vulnerability revealed through Google's irresponsible disclosure program nearly expire before issuing a supposed fix to their uTorrent software. To ensure a timely upgrade panic the details and a demonstration of the vulnerability are already available (archived).
Reluctant to relinquish its tried and true status as THE day-late-dollar-short member of not yet Great Again American automakers; Fiat Chrysler Automobiles (FCA) announced today that it would be following in the footsteps of General Motors in recalling a great many of its great trucks for a "software error" that could end in a smushy death.
Affecting RAM 1500 and 2500 trucks built from 2013-2016 as well as big mother RAM 3500 trucks built from 2014-2016, over one million units will be recalled starting next month, significantly more than the number affected by FCA's Hot Death but only a quarter of GM's numbers from 2016.
The Dodge "software error" has been implicated in at least one death to date when side airbags and seat belt pretensioners failed to activate following an underbody collision leading to a vehicle rollover. No word on whether Dodge's engineers were also responsible for bugs in other TBTF products of Not Yet Great Again. Also no word on whether Herr Trump is planning to extend his recent Executive Order to include automakers but it would be pretty sweet if he did.
Fresh on the heels of an arresting alleged hacker Peter Levashov in Spain, the Department of Justice announced plans to disable a botnet – known as Kelihos – they claim was under his control and used to send spam emails and infect systems with ransomware. Acting assistant attorney-general Kenneth Blanco said the operation will "redirect Kelihos-infected computers to a substitute server", in order to block communications between infected devices and the botnet server, instead redirecting the compromised machines to the DOJ's own botnet servers. Levashov reportedly had been operating the botnet since 2010, and targeted computers running all variants of Microsoft Windows, the preferred target OS of botnet harvesters worldwide. The Department of Justice statement concluded by stating that "The US government will share samples of the malware with antivirus vendors in facilitate updates to their programs which will allow them to detect and remove Kelihos" while leaving government backdoors firmly in place.
The "Bitcoin Unlimited" node count experienced a very sharp ~65% drop around 7:30 PM UTC as a remote-crash vulnerability was made public on Twitter. The node count, as reported by coin.dance, fell to 259 from a previous measurement of 764 moments earlier.
The actual vulnerability is a result of the ineptitude of the "Bitcoin Unlimited" developers to incorrectly implement the usual "monkey see, monkey do" approach to software, by messing up the copy-pasting of power-rangerolade.
Peter Todd's straight Twitter disclosure was made in a context of heightened tensions among the two main flavors of idiocy, namely the SegWit peddlers and the Roger Verified "Bitcoin Unlimited" followers.
As mentioned in Shinohai's latest shitcoin Roundup, a few single language Chinese miners have taken to expressing an unjustified degree of loyalty to yet another doomed anti-Bitcoin forking effort. In the same week the fork effort's defective client unintentionally fell out of consensus due to its inherent slop, Andrew Quentson (WOT:nonperson) published a purported "cosmetically corrected" interview with Jiang Zhuoer (WOT:nonperson) where among other things Zhuoer confesses to "SPV mining" while asserting to have 100 million dollars1 committed to destroying any actual Bitcoin network which remains after splitting his favored altcoin from Bitcoin.