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

[Tenable Vuln Management]: Validation error for VulnerabilityFinding 'scan.target' Field required #3574

Open
romain-filigran opened this issue Mar 6, 2025 · 2 comments
Assignees
Labels
bug use for describing something not working as expected filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran.
Milestone

Comments

@romain-filigran
Copy link
Member

romain-filigran commented Mar 6, 2025

Description

Some errors are observed when ingesting findings from Tenable Vulnerability Management solution.

Traceback (most recent call last): File "/opt/opencti-connector-tenable-vuln-management/tenable_vuln_management/connector.py", line 171, in _process VulnerabilityFinding.from_api_response_body( File "/opt/opencti-connector-tenable-vuln-management/tenable_vuln_management/models/tenable.py", line 402, in from_api_response_body return [cls(**item) for item in joined_data] ^^^^^^^^^^^ File "/usr/local/lib/python3.12/site-packages/pydantic/main.py", line 214, in __init__ validated_self = self.__pydantic_validator__.validate_python(data, self_instance=self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ pydantic_core._pydantic_core.ValidationError: 1 validation error for VulnerabilityFinding scan.target Field required [type=missing, input_value={'schedule_uuid': 'templa...4e25-9300-59db1286f4c2'}, input_type=dict] For further information visit https://errors.pydantic.dev/2.10/v/missing

Environment

OpenCTI version: 6.5.4

Contact me if more information are required

@romain-filigran romain-filigran added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 6, 2025
@romain-filigran romain-filigran added this to the Bugs backlog milestone Mar 6, 2025
@helene-nguyen helene-nguyen added the filigran support [optional] use to identify an issue related to feature developed & maintained by Filigran. label Mar 7, 2025
@flavienSindou
Copy link
Contributor

Seems related to : #3542

@flavienSindou
Copy link
Contributor

Seems related to : #3542

TL;DR : when retrieving findings from the API, an asset should be linked and its ip/domain indicated via last_scan_target attribute. The API seems not to consistently return this attribute anymore compared to what was observed during connector development. Though this attribute can be used to ensure API response consistency, it is not used or processed to create OCTI objects.

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 support [optional] use to identify an issue related to feature developed & maintained by Filigran.
Projects
None yet
Development

No branches or pull requests

3 participants