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

Sample ref not created when importing a bundle STIX #6275

Closed
explorecti opened this issue Mar 5, 2024 · 6 comments · Fixed by #6337
Closed

Sample ref not created when importing a bundle STIX #6275

explorecti opened this issue Mar 5, 2024 · 6 comments · Fixed by #6337
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)
Milestone

Comments

@explorecti
Copy link

Description

When a user manually ingests a STIX bundle containing a file SCO and a Malware SDO with a sample_refs property containing the STIX ID of the file SCO, a "sample" relationship is not created between the file SCO and Malware SDO.

Environment

  1. OS version: CENTOS 7.9
  2. OpenCTI version: 5.12.32
  3. OpenCTI client: frontend

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Manually ingests a STIX bundle containing a file SCO and a Malware SDO with a sample_refs property containing the STIX ID of the file SCO.

Expected Output

A "sample" relationship should be created between the file SCO and Malware SDO.

Actual Output

No relationship is created

Workaround

No work around.

@explorecti explorecti added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 5, 2024
@jborozco jborozco added needs more info Intel needed about the use case and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 7, 2024
@jborozco
Copy link
Member

jborozco commented Mar 7, 2024

@explorecti could you provide us this STIX Bundle so we can try to reproduce the issue ?

@SamuelHassine SamuelHassine added this to the Release 6.0.6 milestone Mar 7, 2024
@explorecti
Copy link
Author

Do to the nature of the STIX data that request is not possible. Please advise further steps if you cannot reproduce the issue, thank you.

@jborozco
Copy link
Member

We created a STIX Bundle to reproduce the issue here:
2024-03-11T09 49 45.944Z_TLP ALL_(ExportFileStix2)_Report-Test_full.json

@explorecti
Copy link
Author

explorecti commented Mar 11, 2024

Perfect @jborozco thank you for taking the time to troubleshoot this issue further. Will this be corrected for the platform 6.0.6 release?

@jborozco
Copy link
Member

@explorecti from the file we created, It seems that you need a proper SRO in your bundle to create a relationship.

sample_ref is an SDO attribute proper to malwares, but it is not enough to create a relationship in the platform.

@explorecti
Copy link
Author

explorecti commented Mar 11, 2024

@jborozco The "sample_ref": [ "file--9be6a529-5444-45e3-8f8c-dd173ca44be7" ] attribute was created and linked to "type": "malware" and "id": "malware--9gh7n530-5278-86e3-7g9b-gg375hj43be9". The issue still remains.

@jborozco jborozco removed the needs more info Intel needed about the use case label Mar 12, 2024
@Jipegien Jipegien modified the milestones: Release 6.0.6, Release 6.0.7 Mar 12, 2024
@JeremyCloarec JeremyCloarec self-assigned this Mar 12, 2024
@JeremyCloarec JeremyCloarec linked a pull request Mar 14, 2024 that will close this issue
5 tasks
@Jipegien Jipegien modified the milestones: Release 6.0.7, Release 6.0.8 Mar 14, 2024
@Kedae Kedae added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 20, 2024
@Jipegien Jipegien changed the title SCO & Malware SDO Sample ref not created when importing a bundle STIX Mar 20, 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 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.

6 participants