As HN: RustDesk Installs Chinese Root Certificates
I'm not an expert in security, but I noticed that the Windows version of RustDesk (https://rustdesk.com/), an open-source remote desktop software, installs a Chinese root certificate to the Windows `Trusted Root Certification Authorities` with all purposes enabled. There's a discussion on GitHub (https://github.com/rustdesk/rustdesk/discussions/6444) where one of the maintainers states the certificates are for driver code signing, but doesn't explain why they need to be placed in `Trusted Root Certification Authorities` with all purposes permissions instead of just for code signing. Does anyone more experienced in security have a take on this?
(
18 comments
| 19 points
| on HN
)
Always be cautious of trusting certs of any kind, especially test/dev certs with top level privileges lol personally i would avoid.
Based on the issue there are too many weak points and the "response" given didnt seem to care about the vulnerabilities or user concerns, only said why its needed...
The issue poster was smart in running in a sandbox and comparing files.
"Yet another remote desktop software, written in Rust. Works out of the box, no configuration required. You have full control of your data, with no concerns about security"....
Yikes. Please don't believe in every repo face value. Your best bet is to generate your own certs (https://github.com/FiloSottile/mkcert) and sign the dlls yourself.
You should never install a root certificate from someone, unless you want them to be able to silently MITM any TLS connection from your machine.
Man-in-the-Middle (MitM) Attacks: If the certificate is not secure, it could be used to intercept and decrypt secure communications without detection, allowing an attacker to read or modify sensitive data in transit.
Impersonation: The app could use the insecure certificate to impersonate legitimate websites or services, potentially tricking users into divulging sensitive information such as login credentials or personal data.
Trust Chain Compromise: Since the Trusted Root Certification Authorities store is used to establish trust for other certificates, an insecure root certificate could be used to issue fraudulent certificates for any domain, which would be trusted by the system.
Malware and Phishing: Malicious software could use the insecure certificate to establish a seemingly secure connection, making phishing attacks and malware distribution more convincing and harder to detect.
Bypassing Security Features: An insecure certificate in the Trusted Root store can undermine security features like HTTPS and code signing, allowing malicious actors to bypass these protections and deliver malware or execute man-in-the-middle attacks without triggering security warnings.
Compliance Violations: Installing insecure certificates in the Trusted Root store may violate security policies and regulatory compliance requirements, potentially leading to legal and financial repercussions.
System Integrity: The presence of an insecure certificate can indicate that the system's integrity has been compromised, which could be part of a broader security breach.
This is something that the OS should be at some regularity reminding the user that has happened. It is not reasonable for a user to assume that installing an application is just going to let that application completely switch the trusts on the computer.
This is an unfortunate side effect of how installation works on Windows I think.
I really think we need to move closer to requesting permissions to specific things rather than a binary “admin or not”.
(When it does suffice, the approach has always been generate a CA certificate on the device itself and install that, generate a cert signed by that CA to sign the code/driver with, then nuke the CA's private keys so they can't be used to sign anything else again. There would be zero need to ever use a real CA here.)
"Frankly, as for 1,2, we do not know either, we are not expert in this field, maybe because it is test cert. As for 3, dll is OV cert, but the driversigning requires EV cert, we do not have EV cert, so we use test cert as a workaround. Someone in HN does not believe we do not have EV, but we really have not. :( But now I think it is time for us to get one."
https://i.ibb.co/bHjMYWH/2024-02-08-00h41-11.png