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

Vulnerabilities default last scan date not displayed properly #4959

Closed
asteriscos opened this issue Dec 5, 2022 · 3 comments · Fixed by #4975, #4976 or #4977
Closed

Vulnerabilities default last scan date not displayed properly #4959

asteriscos opened this issue Dec 5, 2022 · 3 comments · Fixed by #4975, #4976 or #4977
Assignees
Labels
type/bug Bug issue

Comments

@asteriscos
Copy link
Member

Wazuh Elastic Rev Security
4.x 7.x 4xxx Basic, ODFE, Xpack
Browser
Chrome, Firefox, Safari, etc

Description
The last scan date format has changed and this causes a workaround to prevent showing the default date returned by Wazuh API.

This lines should be updated to detect the default date and show - whenever no scan is run.

https:/wazuh/wazuh-kibana-app/blob/v4.3.10-7.10.2/public/components/agents/vuls/inventory/detail.tsx#L172
https:/wazuh/wazuh-kibana-app/blob/v4.3.10-7.10.2/public/components/agents/vuls/inventory.tsx#L179

Preconditions

  1. No vulnerability scan has ever ran.

Steps to reproduce

  1. Navigate to Vulnerabilities / Inventory
  2. See the Last Scan dates

Expected Result

  1. Should show - when no scan was ever executed

Actual Result

  1. Shows default database date

Screenshots

Screenshot from 2022-12-05 12-35-28

@davidjiglesias
Copy link
Member

Does this replicate in v4.3.X?

@yenienserrano
Copy link
Member

In 4.3.9 it has the expected behavior

image

@Desvelao
Copy link
Member

Changes

  • Fixed for vulnerabilities inventory and flyout with details

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment