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

IP / Domain relationships go the wrong way #1112

Closed
securitiz opened this issue Feb 25, 2021 · 1 comment
Closed

IP / Domain relationships go the wrong way #1112

securitiz opened this issue Feb 25, 2021 · 1 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)
Milestone

Comments

@securitiz
Copy link

Description

The relationship between Domain and IPv4 observables goes the wrong way. Currently it allows the "resolves to" relationship from the IP to the domain, which isn't in accordance with STIX. It doesn't allow a domain to resolve to the IP, as it should. (Also STIX doesn't allow these relationships to be created at all - see #1108

Environment

  1. OS (where OpenCTI server runs): Ubuntu 20.04
  2. OpenCTI version: OpenCTI 4.2.4
  3. OpenCTI client: frontend
  4. Other environment details: demo

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create an IPv4 observablein a Report
  2. Create a Domain observable in a Report
  3. Create a relationship from the Domain to the IP

Expected Output

The ability to create a "resolves to" relationship

Actual Output

Only the ability to create a "related to" relationship

Additional information

{ Any additional information, including logs or screenshots if you have any. }

@SamuelHassine
Copy link
Member

Hello @securitiz,

Thanks for reporting, this was indeed a bug. It has been fixed, nevetheless, for the moment, relationships between observables cannot be created in the context of a report. You should create this relation from here:

https://demo.opencti.io/dashboard/observations/observables/e1cc37d1-27ed-43b7-b2d0-5a8894791809

Kind regards,
Samuel

@SamuelHassine SamuelHassine added 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) labels Feb 25, 2021
@SamuelHassine SamuelHassine added this to the Release 4.2.4 milestone Feb 25, 2021
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