[玛丽]2018 年的旧 Trust Wallet iOS 漏洞可能仍会影响某些账户

根据 SECBIT 实验室安全研究人员最近的一份报告，Trust Wallet iOS 应用程序中的一个旧漏洞可能仍然会影响使用该应用程序创建帐户的个人，即使他们不再使用 Trust Wallet。

研究人员表示，该漏洞仅存在于2018年2月5日至8月21日期间，不会影响该时间段之后创建的帐户。

然而，一些用户可能不知道该漏洞的存在，并且可能仍然计划使用暴露的钱包。

该漏洞是由 Trezor 库中 Trust 钱包调用的两个函数引起的，这两个函数本应仅用于测试。

然而，SECBIT 声称，尽管开发者注释警告开发者不要使用这些功能，Trust Wallet 却意外地将这些功能包含在其 iPhone 钱包应用程序中。

据称，此错误使攻击者能够猜测某些用户的私钥并窃取他们的资金。

据 SECBIT 称，即使现在这些账户仍然容易受到攻击。

据称，这个新发现的漏洞与 Trust Wallet 的浏览器扩展缺陷是独立且不同的，Trezor 团队已于 2023 年 4 月承认了这一缺陷。

Trust Wallet 在 2 月 15 日回应 SECBIT 指控的博客文章中表示，该漏洞仅影响了几千名用户，这些用户都已收到通知并迁移到新钱包。

Trust Wallet 声称已于 2018 年 7 月修复了该漏洞，目前其应用程序可以安全使用。

SECBIT 在 Trust Wallet iOS 应用程序中发现漏洞

研究团队表示，他们在调查 2023 年 7 月 12 日发生的一次针对加密钱包的广泛攻击时发现了该漏洞，该攻击影响了 200 多个加密货币账户。

许多受到攻击的帐户已经几个月没有使用过，或者存储在无法访问互联网的设备上，这应该使它们极难被黑客攻击。

此外，受害者还使用了许多不同的钱包应用程序，其中最常用的是 Trust Wallet 和 Klever Wallet。

这使得黑客攻击的原因很难查明，这激起了研究人员的好奇心。

经过进一步调查，研究人员发现，大多数受害者地址在 2018 年 7 月至 8 月期间首次收到了资金。然而，他们的调查在这一发现后不久就陷入了僵局，并转向了其他研究。

随后，2023 年 8 月 7 日，Distrust 网络安全团队宣布据称在 Libbitcoin Explorer 比特币 (BTC) 应用程序中发现了一个漏洞。

这个 Libbitcoin 漏洞被称为“Milk Sad”，允许攻击者猜测用户的私钥。

在了解了这一所谓的缺陷后，SECBIT 团队开始怀疑类似的缺陷可能导致了 7 月 12 日的攻击。

The researchers reopened the investigation and began looking through versions of the Trust Wallet code published from July through August 2018. They discovered that the iOS versions of the app from this period used functions “random32()” and “random_buffer()” from Trezor’s crypto iOS library to generate mnemonic phrases.

These functions had developer notes warning against their use in production apps. For example, the notes for random32() stated, “The following code is not supposed to be used in a production environment. [...] It’s only included to make the library testable. [...] The message above tries to prevent any accidental use outside of the test environment.”

After investigating the code, the researchers allegedly discovered that it generated seed words that were not random enough to prevent them from being guessed by an attacker. This meant that any Trust Wallet account generated on an iOS device during this time was at risk of being drained, SECBIT claimed.

Related: US investigates Trust Wallet iOS app for vulnerability

In its report, SECBIT claimed to have generated a database of compromised addresses, which it then forwarded to the Trust Wallet team. It also claimed to have compared these addresses with the victims of the July 12 hack and found that 83% of the victims had wallets generated using the random32() and random_buffer() functions.

When Trust Wallet was confronted with this information, it allegedly told SECBIT it had already notified users privately in 2018. It also emphasized that the addresses had balances of zero and, therefore, could not be warned against losing funds. SECBIT alleged it urged Trust Wallet to publicly announce the vulnerability but that Trust Wallet did not comply. The firm says it published its findings only after Trust Wallet failed to make this public disclosure.

Despite its critical report, SECBIT pointed out that Trust Wallet is open-source, so some other wallet developer may have forked the code and caused its users to generate vulnerable addresses, or another wallet developer may have independently made the same mistake as Trust Wallet by using the Trezor crypto iOS library from this period to generate addresses. Researchers opined:

“Of course, the Trust Wallet may not be the only one who misused the trezor-crypto library. There may be many other unknown projects that have similar vulnerabilities. Someone could even blame the trezor-crypto library for quietly changing to an insecure default implementation, causing fatal flaws in projects that use it as an underlying dependency.”

According to SECBIT, Trezor updated its library on July 16, 2018, adding production-ready versions of the two functions. Even so, the vulnerability may still affect some users who created accounts in early 2018 but have never sent funds to them, the researchers claimed.

Trust Wallet’s response

Cointelegraph reached out to Trust Wallet for comment. In response, a representative pointed to the team’s Feb. 15 public statement about the issue. In this statement, the development team emphasized that the current version of Trust Wallet does not contain the vulnerability.

“We want to assure Trust Wallet users that their funds are safe and the wallets are safe to use,” the spokesperson stated. “Though there was a previous vulnerability in our open-source code in early 2018 affecting a few thousand users only,” they continued, “the vulnerability was quickly patched with the support of the security community — and affected users were notified and migrated into safe wallets.”

Trust Wallet pushed back against claims that it had not adequately informed users. “Trust Wallet’s founder took swift and proactive steps to inform all impacted users and provided them with a secure migration path,” said the spokesperson, “ensuring no user was left vulnerable.”

Trust Wallet also denied that most of the hacks were against accounts its app generated. Only “600 addresses out of the 2,000s hacked” were found in its user database, implying that most victims were not Trust Wallet users. Of these 600 users, some of them could have imported their addresses from another app, Trust Wallet claimed.

In contrast to SECBIT’s statement that 83% of the victim addresses were produced by the flawed code, Trust Wallet stated that “only one-third of them have the 2018 Trust Wallet historical vulnerability.” In its report, the team encouraged security researchers to make use of its bug bounty program and claimed that it is committed to keeping its wallet secure.

Related: Trust is the best strategy in crypto bear market — Trust Wallet CEO

In a July 12, 2023 report, the Klever wallet also confirmed that some of the victims of the attack had used its app. However, it claimed that all of the addresses had been imported and were not originally created by Klever.

Cointelegraph reached out to Trezor for comment. In response, the firm’s chief technology officer, Tomáš Sušánka, emphasized that the function at the core of the controversy was solely meant for testing and not for official project development use:

“[The function is] exactly as described in the source code, the function is not meant to be used in a production environment, and we provide explicit warnings of this. The function is replaced with a secure RNG on the Trezor itself. This function is meant solely for testing. We love open-source, but it is unrealistic to expect us to prevent any possible misuse of the many projects we have open-sourced. These projects are provided as is, without any warranties, as their licenses clearly depict.”

在 SECBIT 的报告中，研究人员警告在此期间拥有 Trust Wallet 账户的 iOS 用户迁移到新钱包并停止使用旧钱包。

他们表示：“令人担忧的是，用户可能仍然使用在脆弱时期创建的钱包。”

“如果没有意识到这个问题，他们可能会面临进一步的资金损失。”

热点：iOS TRUST WALLET 玛丽 账户