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.

Sign up for GitHub

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

Jump to bottom

[Connector] Recorded Future connector crashes with unmanaged "None" criticality score #1984

Closed
NiQuintin opened this issue Mar 14, 2024 · 3 comments · Fixed by #1976
Closed

[Connector] Recorded Future connector crashes with unmanaged "None" criticality score #1984

NiQuintin opened this issue Mar 14, 2024 · 3 comments · Fixed by #1976
Assignees
@helene-nguyen
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
Release 6.0.9

Comments

@NiQuintin
Copy link

Description

The EI Recorded Future connector crashes following an exception probably due to the non-management of the "None" criticality score, which is not currently processed.

Environment

N/A

Reproducible Steps

See ticket OCTI1-508

Expected Output

N/A

Actual Output

N/A

Additional information

N/A

Screenshots (optional)
@NiQuintin NiQuintin added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 14, 2024
@nino-filigran
Copy link

@helene-nguyen or @Megafredo are you able to reproduce?

@Megafredo
Copy link
Member

Yes @nino-filigran, no problem, it was seen! we can take care of it!

@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label Mar 15, 2024
@helene-nguyen helene-nguyen self-assigned this Mar 15, 2024
@nino-filigran nino-filigran added needs more info Intel needed about the use case and removed needs more info Intel needed about the use case labels Mar 15, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.8 milestone Mar 20, 2024
@Jipegien Jipegien modified the milestones: Release 6.0.8, Release 6.0.9 Mar 20, 2024
@helene-nguyen
Copy link
Member

The bug can be reproduced:

image

It will be corrected today :)

@helene-nguyen helene-nguyen mentioned this issue Mar 25, 2024
Merged
4 tasks
@helene-nguyen helene-nguyen linked a pull request Mar 25, 2024 that will close this issue
[Recorded Future] Fix risk rules criticality score, handle empty string #1976
Merged
4 tasks
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 26, 2024
@SamuelHassine SamuelHassine transferred this issue from OpenCTI-Platform/opencti Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@helene-nguyen helene-nguyen

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
Milestone
Release 6.0.9
Development

Successfully merging a pull request may close this issue.

[Recorded Future] Fix risk rules criticality score, handle empty string OpenCTI-Platform/connectors
7 participants
@SamuelHassine @Megafredo @jborozco @helene-nguyen @Jipegien @nino-filigran @NiQuintin