Skip to content
This repository has been archived by the owner on Apr 26, 2021. It is now read-only.

Rooter Recieving New iproute2 Error, cannot configure Cuckoo to use VPN following documentation #3134

Open
utkonos opened this issue Nov 7, 2020 · 4 comments

Comments

@utkonos
Copy link
Contributor

utkonos commented Nov 7, 2020

My issue is:

Using iproute2 v.5, the following error is returned when the rooter runs this command via subprocess:

# ip route list table tun0
Error: ipv4: FIB table does not exist.
Dump terminated
My Cuckoo version and operating system are:

2.0.7 on Ubuntu 20.04

This can be reproduced by:

Configure vpn to be on according to the documentation.

The log, error, files etc can be found at:

Error: ipv4: FIB table does not exist.
Dump terminated

@mfc
Copy link

mfc commented Jan 20, 2021

maybe rename this issue "cannot configure Cuckoo to use VPN following documentation" in order raise visibility... seems like a pretty big issue.

@utkonos utkonos changed the title Rooter Recieving New iproute2 Error Rooter Recieving New iproute2 Error, cannot configure Cuckoo to use VPN following documentation Jan 20, 2021
@utkonos
Copy link
Contributor Author

utkonos commented Jan 20, 2021

Here is the root cause of this issue:

When Cuckoo starts, this command is sent to the rooter:

rooter("rt_available", entry.rt_table)

The rooter then issues the following command via subprocess:

ip route show table default

The result of this command is the following error:

The result of this command is an error:
Error: ipv4: FIB table does not exist.
Dump terminated

According to the maintainers of the upstream iproute2, this is a new error and behavior for iproute2. There is a thread on their mailing list about the above:
https://www.spinics.net/lists/netdev/msg559739.html

@mfc
Copy link

mfc commented Jan 20, 2021

thanks for the mailing list reference for further info. sounds like the easiest place to fix this issue is within cuckoo to have the rooter subprocess issue a different command or be able to handle the error.

i will try to escalate with cuckoo devs, as no VPN = clear communication to potential adversary that analysis is being performed (either via Tor or clearnet).

@mfc
Copy link

mfc commented Jan 21, 2021

after discussing with Hatching folks, easiest step would be to use Ubuntu 18.04 LTS instead. will probably be a while before the Cuckoo dev community move to a later Ubuntu LTS and start fixing issues like this unfortunately (18.04 LTS supported until April 2023).

mfc added a commit to mfc/cuckoo that referenced this issue Feb 25, 2021
because of issues such as: cuckoosandbox#3134 with current Ubuntu 20.04 TLS.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants