openiocimport module fail
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 377
- Forks
- 280
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 10
Description
I am getting the following error when using the openiocimport module.
ERROR:misp-modules:Something went wrong:
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/misp_modules/__init__.py", line 197, in post
response = yield tornado.gen.with_timeout(timeout, self.run_request(jsonpayload))
File "/usr/local/lib/python3.5/dist-packages/tornado/gen.py", line 1099, in run
value = future.result()
File "/usr/lib/python3.5/asyncio/futures.py", line 274, in result
raise self._exception
File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.5/dist-packages/misp_modules/__init__.py", line 185, in run_request
response = mhandlers[x['module']].handler(q=jsonpayload)
File "/usr/local/lib/python3.5/dist-packages/misp_modules/modules/import_mod/openiocimport.py", line 43, in handler
pkg = openioc.load_openioc(package)
File "/usr/local/lib/python3.5/dist-packages/pymisp/tools/openioc.py", line 179, in load_openioc
if not misp_event.info:
AttributeError: 'MISPEvent' object has no attribute 'info'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in misp_modules/modules/import_mod/openiocimport.py at handler and follow the call into pymisp/tools/openioc.py, where load_openioc raises the reported AttributeError. Reproduce the failure with an OpenIOC package and inspect the MISPEvent API used there. Done means the openiocimport module completes the import without this exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100