TheHive-Project / TheHive-Project/Cortex-Analyzers

[Bug] FalconCustomIOC responder Not working

Open
#904 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

category:bug help wanted scope:responder
Dominant language
Python
Stars
490
Forks
405
Avg merge
2d 43m
Merged PRs (30d)
8

Description

Describe the bug
Installing FalconCustomIOC responder and configure it by adding the Client ID and secret key in Cortex.
When executing the responder from TheHive, there isn't any result shows and shows failed as result

To Reproduce
Steps to reproduce the behavior:

  1. Configure FalconCustomIOC responder by adding the Client ID and secret key in Cortex GUI
  2. Go to an observable to theHive and run the responder

Expected behavior
The observable should be added to IOC list in CrowdStrike.

Complementary information
Error message in responder details:
"errorMessage": "Unexpected end-of-input within/between Object entries\n at [Source: (sun.nio.ch.ChannelInputStream); line: 1, column: 1257]"

Work environment

  • Client OS: Windows 10
  • Server OS: Linux
  • Browse type and version: Firefox
  • Cortex version: 3.0.0-1
  • Cortex Analyzer/Responder name: FalconCustomIOC
  • Cortex Analyzer/Responder version: 1.0

Possible solutions
If applicable, indicate possible solutions to the problem.

Additional context
Add any other context about the problem here.

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

No file or test is named in the issue. Start by reproducing the FalconCustomIOC responder failure from TheHive with Cortex 3.0.0-1 and inspect the responder details for the JSON parsing error. Done means the observable is added to CrowdStrike's IOC list without a failed result.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.