EVE-NG Pro 3.0.1-17 update is out

The EVE-NG Team just released the latest Update for the Pro Edition.

  • New templates for Catalyst 8000, FreeNAS, Android, and many more
  • Template updates
  • Node icons library

The update also fixed a “security flaw” in guacamole, where the guacadmin password was still set to “guacadmin.” Apparently, not many users were aware of that, and some even put the EVE straight into the www instead of having a decent firewall between the EVE and the www.

Seriously, guys – it’s 2021 – this should not even be a concern.
Exposing a Solution to the www without changing every tiny setting and password is like crying out loud, “hack me fast plz” – this happens automated nowadays, by the way!

My advice is always to have a decent Firewall between you (somewhere in the www) and your Lab.
Use a VPN to connect to it, and you are safe!

And to all the Users out there calling it a “backdoor” or “hack of the century”:

I suggest you first learn what a backdoor is and then start flaming 😉
May I recommend https://en.wikipedia.org/wiki/Backdoor_(computing)?
If you are lazy, here’s a summary: Backdoor means bypassing normal authentication or encryption – this was never the case here. It was just a default user that allowed this – nothing fancy… This user’s password is “scrambled” now, so you don’t need to cry anymore…
Shoutouts to the copycats from pnetlab who tried so hard to throw some dirt 😉

If you use IPv6 only (like me), make sure to change the ovfstartup script (opt/ovf/ovfstartup.sh) after the update so that your Server is reachable via v6 again:

#Disable ipv6 on EVE Host
grep -q 'ipv6.*0' /opt/unetlab/html/includes/config.yml 2>/dev/null && sysctl -w net.ipv6.conf.all.disable_ipv6=1
grep -q 'ipv6 ' /opt/unetlab/html/includes/config.yml 2>/dev/null || sysctl -w net.ipv6.conf.all.disable_ipv6=1
<strong>grep -q 'ipv6.*1' /opt/unetlab/html/includes/config.yml 2>/dev/null && sysctl -w net.ipv6.conf.all.disable_ipv6=0</strong>

The last line is important – save the changes and reboot your server.
Your IPv6 should be reachable again 🙂
That’s all I have for you today – stay safe, folks!

Leave a Reply

Your email address will not be published. Required fields are marked *

Captcha * Time limit is exhausted. Please reload CAPTCHA.