TheHive-Project / TheHive-Project/Cortex

MailIncidentStatus Responder Error: argument None type

Open
#452 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
1.6k
Forks
264
PR merge metrics
No merged PRs in 30d

Description

After running MailIncidentStatus Responder in theHive there is Error in Cortex and Failure status:
Traceback (most recent call last): File "/opt/cortex/Cortex-Analyzers/responders/MailIncidentStatus/mailincidentstatus.py", line 359, in MailIncidentStatus().run() File "/opt/cortex/Cortex-Analyzers/responders/MailIncidentStatus/mailincidentstatus.py", line 47, in run self.validate_Config() File "/opt/cortex/Cortex-Analyzers/responders/MailIncidentStatus/mailincidentstatus.py", line 122, in validate_Config if "." not in domain:TypeError: argument of type 'NoneType' is not iterable

After the problematic lines were commented out for checking, the same Error was repeated in line 131:
image

Cortex is connected with theHive, Config is filled in:
image

The latest version of files from Git repo TheHive-Project/Cortex-Analyzers were used. Does anyone know what the problem is?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with responders/MailIncidentStatus/mailincidentstatus.py, especially validate_Config() around lines 47, 122, and 131, and review the traceback and configuration shown in the issue. Reproduce the responder run with the reported configuration and determine which value is None; done means the responder no longer raises the reported TypeError and reaches the expected status.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.