Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CrowdStrike TIP] "'FetchedReport' object is not subscriptable" error on Indicator #2603

Closed
Lhorus6 opened this issue Sep 5, 2024 · 0 comments · Fixed by #2676
Closed

[CrowdStrike TIP] "'FetchedReport' object is not subscriptable" error on Indicator #2603

Lhorus6 opened this issue Sep 5, 2024 · 0 comments · Fixed by #2676
Assignees
Labels
bug use for describing something not working as expected filigran team use to identify PR from the Filigran team solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@Lhorus6
Copy link
Contributor

Lhorus6 commented Sep 5, 2024

Description

For the CrowdStrike import connector

The connector raises errors on many indicators.

NB: I think the “Discarding indicator XXX bundle” error follow from the previous failed. Without the fail, there would be no discard. So we can ignore them, it's normal.

Here's an example log:

Traceback (most recent call last): File "/opt/opencti-connector-crowdstrike/crowdstrike_feeds_connector/indicator/importer.py", line 241, in _create_indicator_bundle return bundle_builder.build() ^^^^^^^^^^^^^^^^^^^^^^ File "/opt/opencti-connector-crowdstrike/crowdstrike_feeds_connector/indicator/builder.py", line 538, in build reports = self._create_reports(object_refs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/opencti-connector-crowdstrike/crowdstrike_feeds_connector/indicator/builder.py", line 425, in _create_reports indicator_report["report"], indicator_report["files"], objects ~~~~~~~~~~~~~~~~^^^^^^^^^^ TypeError: 'FetchedReport' object is not subscriptable

I've spoken to @Megafredo about this

Environment

OCTI 6.2.18

@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Sep 5, 2024
@Lhorus6 Lhorus6 changed the title [CrowdStrike TIP] 'FetchedReport' object is not subscriptable [CrowdStrike TIP] 'FetchedReport' object is not subscriptable error on Indicator Sep 5, 2024
@Lhorus6 Lhorus6 changed the title [CrowdStrike TIP] 'FetchedReport' object is not subscriptable error on Indicator [CrowdStrike TIP] "'FetchedReport' object is not subscriptable" error on Indicator Sep 5, 2024
@romain-filigran romain-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Sep 6, 2024
@romain-filigran romain-filigran added this to the Bugs backlog milestone Sep 6, 2024
@helene-nguyen helene-nguyen added the filigran team use to identify PR from the Filigran team label Sep 19, 2024
@helene-nguyen helene-nguyen linked a pull request Sep 20, 2024 that will close this issue
4 tasks
@labo-flg labo-flg modified the milestones: Bugs backlog, Release 6.3.2 Sep 23, 2024
@helene-nguyen helene-nguyen added the solved use to identify issue that has been solved (must be linked to the solving PR) label Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected filigran team use to identify PR from the Filigran team solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants