You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if it is caused by the Cortex docker image or the analyzer's code, but when the latest MISP_2_0 analyzer is run on an IP, Cortex chokes with the following traceback:
Invalid output
WARNING [__init__.py:49 - <module>() ] Unable to load pymisp properly: No module named enum
Traceback (most recent call last):
File "MISP/misp.py", line 80, in <module>
MISPAnalyzer().run()
File "MISP/misp.py", line 29, in __init__
proxies={'http': self.http_proxy, 'https': self.https_proxy})
File "/opt/Cortex-Analyzers/analyzers/MISP/mispclient.py", line 59, in __init__
self.misp_connections.append(pymisp.PyMISP(url=server,
AttributeError: 'module' object has no attribute 'PyMISP'
Steps to Reproduce
Deploy Cortex as a docker container or Swarm service
Supply latest analyzers as a docker volume
Use MISP_2_0 analyzer on an IP observable
Possible Solutions
Perhaps a dependency issue in Cortex docker image for PyMISP? The only place it imports from enum import Enumis here
The text was updated successfully, but these errors were encountered:
I'm having the same issue still as well. I was able to get it working by deleting the symlink from python->python2 and replacing it with python->python3. It's a pretty dirty fix though
Request Type
Bug
Work Environment
Problem Description
Not sure if it is caused by the Cortex docker image or the analyzer's code, but when the latest
MISP_2_0
analyzer is run on an IP, Cortex chokes with the following traceback:Steps to Reproduce
MISP_2_0
analyzer on an IP observablePossible Solutions
Perhaps a dependency issue in Cortex docker image for PyMISP? The only place it imports
from enum import Enum
is hereThe text was updated successfully, but these errors were encountered: