In the past month, the value of Bitcoin has risen from $18,000 to $20,000. There is news in the currency circle: before Christmas, Bitcoin is bound to rise sharply.
Last night, BTC rushed to the high level of 23,000 very competitively.
Led by the rise of Bitcoin, the currency circle has fallen into a frenzy, and the encrypted digital market is hot. Cryptocurrencies such as Ethereum, Ripple, and Litecoin are also on the rise.
From yesterday evening to today, the currency circle has staged scenes of large-scale true fragrance scenes, and enthusiastic investors in the market have entered the fight one after another.
Compared to 2017s bitcoin frenzy, this rally looks likely to be more stable.
2020 is a special year for everyone. The epidemic broke out and the currency circle was in turmoil. The emergence and development boom of decentralized finance DeFi has made the blockchain start to attract peoples attention again.
secondary title
Bitcoin is soaring, is your wallet still safe?
In recent years, digital wallet security incidents have occurred frequently.
On November 19 last year, Ars Technica reported that two cryptocurrency wallet data were leaked and 2.2 million account information was stolen. Security researcher Troy Hunt confirmed that the stolen data came from the accounts of cryptocurrency wallet GateHub and RuneScape bot provider EpicBot.
This isnt the first time Gatehub has suffered a data breach. In June last year, hackers reportedly compromised around 100 XRP Ledger wallets, resulting in the theft of nearly $10 million in funds.
secondary title
Crypto Wallet Basic Audit Checklist
- How does the application generate a private key?
- How and where does the application store raw information and private keys?
- Is the wallet connected to a trustworthy blockchain node?
- Does the application allow users to configure custom blockchain nodes? If allowed, what impact would a malicious blockchain node have on an application?
- Does the application connect to a centralized server? If yes, what information does the client application send to the server?
- Does the application require the user to set a strong password?
- Does the application require two-factor authentication when users attempt to access sensitive information or transfer money?
- Does the application use vulnerable third-party libraries that can be exploited?
- Are there secrets (eg: API keys, AWS credentials) leaked in source code repositories?
- Are there obvious bad code implementations (such as misunderstandings of cryptography) appearing in the program source code?
- secondary title
Mobile Wallet
Mobile devices such as cell phones are more likely to be lost or stolen than laptops.
- Does the app warn the user not to take screenshots of sensitive data - Do Android apps prevent users from taking screenshots when displaying sensitive data? Do iOS apps warn users not to take screenshots of sensitive data?
- Does the app leak sensitive information in background screenshots?
- Does the app detect if the device is jailbroken/rooted?
- Does the application lock the background servers certificate?
- Does the application record sensitive information in the programs log?
- Does the application contain misconfigured deeplinks and intents, and can they be exploited?
- Does the application bundle obfuscate the code?
- Does the application implement anti-debugging functionality?
- Does the application check for application repackaging?
- (iOS) Does the data stored in the iOS Keychain have sufficient security properties?
- Is the application affected by keychain data persistence?
- Does the application disable the custom keyboard when the user enters sensitive information?
- secondary title
web wallet
- Is the application vulnerable to cross-site scripting (XSS)?
- Is the application vulnerable to clickjacking?
- Does the application have a valid Content Security Policy?
- Does the application have an open redirection vulnerability?
- Is the application vulnerable to HTML injection?
Its rare for web wallets to use cookies these days, but if they do, you should check:
- Does the app contain features other than basic wallet functionality? Are there vulnerabilities in these features that can be exploited?
- secondary title
extension wallet
What permissions does the extension ask for?
How does the extension app decide which websites are allowed to communicate with the extension wallet?
How does the extension wallet interact with web pages?
Can a malicious website use a vulnerability in the extension to attack the extension itself or other pages in the browser?
Can a malicious website read or modify data belonging to an extension without the users consent?
Are extension wallets vulnerable to clickjacking?
Does the extension wallet (usually background script) check the origin of the message before processing it?
secondary title
Electron desktop wallet
Among the desktop wallets tested in the past, about 80% of the desktop wallets are based on the Electron framework. When testing an Electron-based desktop application, not only look for possible vulnerabilities in the web application, but also check that the Electron configuration is secure.
CertiK has targetedElectrons desktop application vulnerabilityanalysis, you can click to visit this article to learn more.
The following are the audit categories to be checked when the Electron-based desktop wallet is evaluated:
What version of Electron does the application use?
Does the application load remote content?
Does the application disable nodeIntegration and enableRemoteModule?
Does the application have the contextisolation, sandbox and webSecurity options enabled?
Does the application allow users to jump from the current wallet page to any external page in the same window?
Does the application implement an effective Content Security Policy?
Does the preload script contain code that could be abused?
Does the application pass user input directly into dangerous functions (such as openExternal)?
secondary title
Server-Side Vulnerability Checklist
More than half of the crypto wallet apps we tested had no centralized server, they were directly connected to blockchain nodes.
The CertiK technical team sees this as a way to reduce the attack surface and protect user privacy.
However, if the application wishes to provide customers with more functionality than account management and token transfer, the application may require a centralized server with a database and server-side code.
- Authentication and Authorization
- KYC and its validity
- race condition
- Cloud server configuration error
- Web server misconfiguration
- Insecure Direct Object Reference (IDOR)
- Server Side Request Forgery (SSRF)
- Insecure file upload
- Any type of injection (SQL, command, template) vulnerability
- Arbitrary file read/write
- business logic error
- rate limit
- denial of service
Summarize
Summarize
Welcome to search WeChat [certikchina] and follow CertiKs official WeChat public account, click on the dialog box at the bottom of the public account, leave a message to get free consultation and quotation!