Security Alert: Multiple Critical Vulnerabilities Discovered on RoyalMix - Follow-up ReportDear RoyalMix users and crypto enthusiasts,
This is a follow-up to my previous security report. I've uncovered additional critical security issues on RoyalMix that I feel compelled to share with the community.
New Issues Discovered:Weak ID system for order retrieval
Exposure of real IP behind DDoS Guard proxy
Direct access via public IP
Vulnerabilities in Apache HTTPD 2.4.52
Consequences:These newly discovered flaws, combined with the previously reported API token exposure, severely compromise user security and anonymity, potentially exposing transactions and personal data.
Technical Details:- Order IDs used to fetch user orders consist of only 6 digits, allowing only 1 million combinations
- The server's real IP is exposed despite using a DDoS proxy
- The site is directly accessible via its public IP, bypassing protections
- Apache HTTPD 2.4.52 is vulnerable to buffer overflow and HTTP request smuggling attacks
Proof:In addition to the API token issue previously reported, I've gathered concrete evidence of these vulnerabilities:
Weak Order ID system: I've observed that order IDs like 633366, 361622, and 962585 are used to fetch user orders. This 6-digit system is highly insecure and susceptible to brute-force attacks.
Censys scan results: I've attached a screenshot from Censys showing sensitive information about the RoyalMix server, including TLS certificate details and the real IP address behind the DDoS protection.
[https://ibb.co/SN3RHsq]
This screenshot reveals:
The domain name (royalmix.io) associated with the IP
ECDSA public key details
Certificate fingerprints
The real IP address: 193.203.190.80
Direct IP access: I was able to access the site directly using the IP address 193.203.190.80, bypassing the DDoS protection.
Apache version: The Censys scan confirms the use of Apache HTTPD 2.4.52, which is known to be vulnerable.
Call to Action:In light of these new findings, I strongly urge the RoyalMix team to:
- Address the API token exposure issue from the previous report
- Completely revise their order identification system to use longer, more secure IDs
- Properly configure their DDoS proxy to mask the real IP
- Disable direct access via IP
- Immediately update Apache HTTPD to the latest stable version
- Conduct a comprehensive security audit of their entire infrastructure
Note: This information is shared in a spirit of responsibility and transparency. The goal is to improve security for all users. I strongly recommend immediate action on both this and the previous report's findings.