vmware-labs / attack-surface-framework

Tool to discover external and internal network attack surface
Other
188 stars 43 forks source link

Subdomains not being discovered #8

Closed sneakyrussianee closed 1 year ago

sneakyrussianee commented 1 year ago

Hello

Subdomains are not being discovered through the web interface. Running vanilla Kali (new install). nohup.out output below.

The only way to force the discovery is to run the subfinder (by copying the command below) manually.

Executing.. subfinder -dL /home/discovery/targets.txt -all -cs -oJ -o /home/discovery/report.txt 2>&1 | tee -a /home/discovery/history/202302011431_discovery.log | grep -e "^{" | python3 manage.py parse_tools --parser=subfinder.output --input=stdin 2>&1 | tee -a /home/discovery/history/202302011431_run.log System check identified some issues:

WARNINGS: ?: (urls.W005) URL namespace 'admin' isn't unique. You may not be able to reverse all URLs in this namespace app.vdInServices: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. app.vdInTarget: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. app.vdJob: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. app.vdNucleiResult: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. app.vdRegExp: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. app.vdResult: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. app.vdServices: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. app.vdTarget: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. done removed '/home/discovery/.lock'

lytran2000 commented 1 year ago

Thanks for reporting the issue. We will be looking into the issue, and inform you any findings.

psc4re commented 1 year ago

Fixed by moving subfinder to docker vs standalone