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

Error when accessing Intrusion sets on a specific platform (missing data) #4095

Closed
SouadHadjiat opened this issue Aug 18, 2023 · 0 comments
Closed
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@SouadHadjiat
Copy link
Member

SouadHadjiat commented Aug 18, 2023

Description

Can't access currently intrusions sets on Filigran platform : https://filigran.opencti.io/dashboard/threats/intrusion_sets
The issue is due to a missing Sector targetted by an intrusion Set of the list (the relationship still exists but the Sector is not found). It only happens in this case, and can also happen for Malwares, Campaigns, and Threat Actors cards views.
It happens also for malwares, just need to scroll a little and the error appears https://filigran.opencti.io/dashboard/arsenal/malwares

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: 5.9.6 (latest)
  3. OpenCTI client: frontend
  4. Other environment details: Filigran platform instance

Reproducible Steps

Steps to create the smallest reproducible scenario:
Didn't reproduce locally yet, I only observed it on Filigran platform.

@SouadHadjiat SouadHadjiat added the bug use for describing something not working as expected label Aug 18, 2023
@SouadHadjiat SouadHadjiat self-assigned this Aug 18, 2023
@SamuelHassine SamuelHassine added this to the Release 5.10.0 milestone Aug 21, 2023
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Aug 23, 2023
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 solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants