Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cve-search not working #249

Closed
d4op opened this issue May 18, 2022 · 15 comments
Closed

cve-search not working #249

d4op opened this issue May 18, 2022 · 15 comments
Labels
cve-search Some cve-search question/issue help wanted Extra attention is needed Installation Installation issues stale

Comments

@d4op
Copy link

d4op commented May 18, 2022

Describe the bug
cve-search not working with docker-compose. installed it using default switch with sudo

To Reproduce
Steps to reproduce the behavior:

  1. EMBA installation using -d switch
  2. all firmwares
  3. Start EMBA with the default parameters from wiki
  4. See error
    error

Linux Debian up to date

@m-1-k-3 m-1-k-3 added the Installation Installation issues label May 18, 2022
@m-1-k-3
Copy link
Member

m-1-k-3 commented May 18, 2022

Currently we have not tested EMBA on Debian (see https://github.com/e-m-b-a/emba/wiki/Installation#prerequisites). But let's give it a try.

Was the installation able to finish without errors?

Probably the hammer works "sudo /etc/init.d/docker restart" or the corresponding command on your debian.

If not, could you please post the output of ifconfig and netstat -anpt

Please try such a search manually:
└─$ ./external/cve-search/bin/search.py -p busybox

and an database update:
└─$ ./external/cve-search/sbin/db_updater.py -v

Please post the output of every command.

@m-1-k-3 m-1-k-3 added the unsupported Unsupported environment label May 18, 2022
@d4op
Copy link
Author

d4op commented May 18, 2022

i use kali, sorry. no debian.
kali is based on debian.

so here are to screenshots.

busybox command doesnt return anything!!!

updater updated all
updateworks

but main tool tells mongo db restarting
bug

@m-1-k-3
Copy link
Member

m-1-k-3 commented May 18, 2022

Could you check the network interfaces with ifconfig. There should be an interface called emba_runs:

emba_runs: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.36.0.1  netmask 255.255.0.0  broadcast 172.36.255.255

If the IP is missing please restart your docker daemon with:

└─$ sudo /etc/init.d/docker restart                     

If these points are fine, your database is probably corrupted. You can try to fix this with a full rebuild

└─$ ./external/cve-search/sbin/db_updater.py -f

@m-1-k-3 m-1-k-3 removed the unsupported Unsupported environment label May 18, 2022
@d4op
Copy link
Author

d4op commented May 20, 2022

999

@m-1-k-3
Copy link
Member

m-1-k-3 commented May 21, 2022

Your network settings are looking fine.

It looks like this issue or this

Please check your internet connectivity and afterwards restart docker, mongod, redis-server and finally purge and repopulate your database

@m-1-k-3 m-1-k-3 added the cve-search Some cve-search question/issue label May 24, 2022
@m-1-k-3
Copy link
Member

m-1-k-3 commented May 25, 2022

Is it now working?

@d4op
Copy link
Author

d4op commented May 25, 2022

no it isnt. i tryed it today on 3 different machines.
2 kali fresh install
1 debian

sudo ./installer.sh -d

and everytime it says the redis and mongodb error.

@m-1-k-3
Copy link
Member

m-1-k-3 commented May 26, 2022

What is your VM spec? RAM and CPU cores?
Redis needs a lot of RAM and CPU cores. As far as I can remember it only works reliable with 4+ cores and 8+gig of RAM

@d4op
Copy link
Author

d4op commented May 29, 2022

its no VM. its a laptop (32 GB RAM, i7) + docker
and a dekstop (32 GB RAM, i7) + docker

@p4cx
Copy link
Member

p4cx commented Jun 17, 2022

Sorry for the late reply. But we have no idea why it's not working on your computer. Are you using EMBA in a Docker container? If that's the case: We don't support that and therefore you have to solve it yourself. If you install it natively on your computers, it should work fine if you follow our instructions. Without further information we cannot support you any further.

@m-1-k-3 m-1-k-3 added the help wanted Extra attention is needed label Jun 22, 2022
@fredjo3
Copy link

fredjo3 commented Jun 23, 2022

I am having the same issue. I'm running a vm of Kali-rolling
uname -a : 5.18.0-kali2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.18.5-1kali1 (2022-06-20) x86_64 GNU/Linux
32 CPUs, 128GB RAM

Errors at installation:
2022-06-23 11:57:40,191 - CVEDownloads - ERROR - Did not receive last-modified header in the response; setting to default (01-01-1970) and force update! Headers received: {'content-length': '93', 'cache-control': 'no-cache', 'content-type': 'text/html', 'connection': 'close'}
2022-06-23 11:57:40,192 - CVEDownloads - ERROR - Unhandled Content-Type encountered: text/html from url
2022-06-23 11:57:40,456 - CVEDownloads - ERROR - Did not receive last-modified header in the response; setting to default (01-01-1970) and force update! Headers received: {'content-length': '93', 'cache-control': 'no-cache', 'content-type': 'text/html', 'connection': 'close'}
2022-06-23 11:57:40,457 - CVEDownloads - ERROR - Unhandled Content-Type encountered: text/html from url

Errors at runtime:
[] CVE-search not working - restarting Mongo database for CVE-search
[] CVE-search not working - restarting Mongo database for CVE-search
cve-search - not ok
[-] The needed CVE database is not responding as expected.
[-] CVE checks are currently not possible!
[-] Please check the following documentation on Github: #187
[-] If this does not help, open a new issue here: https://github.com/e-m-b-a/emba/issues

I cannot for the life of me get the cve-search to work. The issue is that communication with mongo is failing for some reason.
Looking at the interface it shows that emba_runs is down. When I run sudo ip link set emba_runs up and then sudo ip -c a, it reports as being down.

4: emba_runs: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:d2:10:f5:1a brd ff:ff:ff:ff:ff:ff
inet 172.36.0.1/16 brd 172.36.255.255 scope global emba_runs
valid_lft forever preferred_lft forever
inet 172.36.2.0/16 scope global secondary emba_runs
valid_lft forever preferred_lft forever

@m-1-k-3
Copy link
Member

m-1-k-3 commented Jun 23, 2022

Could you try to install cve-search completely from scratch (ideally on a fresh kali) and manually as described here: https://cve-search.github.io/cve-search/getting_started/installation.html?

@m-1-k-3
Copy link
Member

m-1-k-3 commented Jul 4, 2022

In #261 @p4cx has included a new switch (-j) for disabling the cve-search check. Probably this will help in running EMBA without 1day vulnerability discovery mechanisms as a workaround.

@github-actions
Copy link

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the stale label Jul 19, 2022
@github-actions
Copy link

This issue was closed because it has been inactive for 7 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cve-search Some cve-search question/issue help wanted Extra attention is needed Installation Installation issues stale
Projects
None yet
Development

No branches or pull requests

4 participants