Subject: Security Concerns Regarding IP Address Exposure After XDC 2.0 Upgrade
Dear XDC Team,
I hope this message finds you well. I would like to bring to your attention some security concerns that I have encountered following the upgrade to XDC 2.0 on certain nodes.
Upon reviewing the stats of XDC master nodes, I have noticed that many nodes upgraded to XDC 2.0 have their external IP addresses publicly exposed in the format below:
Additionally, it seems that RPC and WebSocket access is available externally, which poses significant security risks. The exposure of these IP addresses could lead to the following potential issues:
Increased risk of DDoS attacks or unauthorized access
We've implemented a fix to address the IP address exposure issue following the XDC 2.0 upgrade. It’s important for all node operators to fetch the latest changes from Git to ensure your node remains secure.
Thank you for your prompt response and for addressing the IP address exposure issue. I have successfully updated my node following the instructions provided.
Additionally, I noticed that the issue with the line "./start-node.sh:/work/start-node.sh" in the docker-compose.yml file has now been correctly changed to "./start-node.sh:/work/start.sh". I was planning to report this today, but I’m glad to see that it has already been fixed.
I truly appreciate the quick action taken by the team.
Best regards,
11ppm
For further actions, you may consider blocking this person and/or reporting abuse
Subject: Security Concerns Regarding IP Address Exposure After XDC 2.0 Upgrade
Dear XDC Team,
I hope this message finds you well. I would like to bring to your attention some security concerns that I have encountered following the upgrade to XDC 2.0 on certain nodes.
Upon reviewing the stats of XDC master nodes, I have noticed that many nodes upgraded to XDC 2.0 have their external IP addresses publicly exposed in the format below:
Additionally, it seems that RPC and WebSocket access is available externally, which poses significant security risks. The exposure of these IP addresses could lead to the following potential issues:
I have also upgraded my node to XDC 2.0, but my node does not exhibit this issue, unlike many others where IP addresses are publicly visible.
Given the potential risks associated with this, I kindly ask for your review of this situation and for guidance on addressing it.
Thank you for your attention to this matter. I look forward to your response and any suggested solutions.
Hello,
The development team is aware of the issue, and we're confident it will be resolved in the next few hours.
Hello,
We've implemented a fix to address the IP address exposure issue following the XDC 2.0 upgrade. It’s important for all node operators to fetch the latest changes from Git to ensure your node remains secure.
Run the following command to update:
bash mainnet/upgrade.sh
Dear Anil and the XDC Team,
Thank you for your prompt response and for addressing the IP address exposure issue. I have successfully updated my node following the instructions provided.
Additionally, I noticed that the issue with the line
"./start-node.sh:/work/start-node.sh"in thedocker-compose.ymlfile has now been correctly changed to"./start-node.sh:/work/start.sh". I was planning to report this today, but I’m glad to see that it has already been fixed.I truly appreciate the quick action taken by the team.
Best regards,
11ppm