Bitcoin Forum

Alternate cryptocurrencies => Speculation (Altcoins) => Topic started by: bbc.reporter on May 30, 2018, 01:07:23 AM



Title: Critical security flaw discovered in EOS
Post by: bbc.reporter on May 30, 2018, 01:07:23 AM
The EOS community said that this was only FUD and that all the vulnerabilities were fixed. But there is another group saying that the EOS development team is not that confident on the platform's security.

Also, there are rumors that there might be a delay on the release of the mainnet.

After EOS dumped all their ETH, and the release of this critical vulnerability, I reckon the most skeptical of you might be thinking of 2 words. Exit Scam.

https://hacked.com/wp-content/uploads/2018/01/eos.jpg

Security researchers have discovered a series of new vulnerabilities in EOS blockchain platform, one of which could allow remote hackers to take complete control over the node servers running the critical blockchain-based applications.

Discovered by Chinese security researchers at Qihoo 360—Yuki Chen of Vulcan team and Zhiniang Peng of Core security team—the vulnerability is a buffer out-of-bounds write issue which resides in the function used by nodes server to parse contracts.

To achieve remote code execution on a targeted node, all an attacker needs to do is upload a maliciously crafted WASM file (a smart contract) written in WebAssembly to the server.

As soon as the vulnerable process parser reads the WASM file, the malicious payload gets executed on the node, which could then also be used to take control over the supernode in EOS network—servers that collect transaction information and pack it into blocks.


Read the full article https://thehackernews.com/2018/05/eos-blockchain-smart-contract.html?m=1


Title: Re: Critical security flaw discovered in EOS
Post by: Javi_Anibarro on May 30, 2018, 03:18:38 AM
lol yeah very funny seeing this actually.
their supporters always said ''it's fud from china" or "fixed" or something like that.
https://www.reddit.com/r/CryptoCurrency/comments/8mwo4c/eos_bugs_discovered_before_mainnet_launch/dzr1eb4/
well i am not surprising to see it because i already seen this on XVG too.
nothing new..