No new database updates since 2024-11-15T07:55:26

[thomasweaver]

The VDB summary is showing the database was last created 2024-11-15T07:55:26+00:00.

[# vdb --download-full-image

         ___

/\ ._ ._ | |_ ._ _ . |
/--\ |) |) | | | | (/ (| |
| |

INFO [2024-12-18 19:21:35,509] Downloading vdb image from ghcr.io/appthreat/vdbxz-10y:v6 to /cache

                        VDB Summary

┏━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Property ┃ Value ┃
┡━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ created_utc │ 2024-11-15T07:55:26+00:00 │
├───────────────────┼─────────────────────────────────────────────┤
│ cve_data_count │ 3823088 │
├───────────────────┼─────────────────────────────────────────────┤
│ cve_index_count │ 3989664 │
├───────────────────┼─────────────────────────────────────────────┤
│ sources │ ['AquaSource', 'OSVSource', 'GitHubSource'] │
├───────────────────┼─────────────────────────────────────────────┤
│ start_year │ 2014 │
├───────────────────┼─────────────────────────────────────────────┤
│ github_page_count │ 20 │
└───────────────────┴─────────────────────────────────────────────┘
Metadata file: /cache/vdb.meta

Database no longer seems to be updated.

[prabhu]

https://github.com/AppThreat/vdb/actions/runs/12412358521/job/34651977523#step:8:84

Traceback (most recent call last):
  File "/home/runner/work/vdb/vdb/vulnerability-db/vdb/cli.py", line 342, in <module>
    main()
  File "/home/runner/work/vdb/vdb/vulnerability-db/vdb/cli.py", line 310, in main
    s.refresh()
  File "/home/runner/work/vdb/vdb/vulnerability-db/vdb/lib/nvd.py", line 214, in refresh
    return self.download_all()
           ^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/vdb/vdb/vulnerability-db/vdb/lib/osv.py", line 61, in download_all
    self.store(data)
  File "/home/runner/work/vdb/vdb/vulnerability-db/vdb/lib/cve.py", line 542, in store
    cve5_list = self.convert5(data)
                ^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/vdb/vdb/vulnerability-db/vdb/lib/cve.py", line 529, in convert5
    containers = Containers(cna=to_cve_containers(avuln))
                                ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/work/vdb/vdb/vulnerability-db/vdb/lib/cve.py", line 465, in to_cve_containers
    metrics=to_metrics(avuln),
            ^^^^^^^^^^^^^^^^^
  File "/home/runner/work/vdb/vdb/vulnerability-db/vdb/lib/cve.py", line 373, in to_metrics
    cvssV3_1=Field1(
             ^^^^^^^
  File "/opt/hostedtoolcache/Python/3.12.8/x64/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 Field1
userInteraction
  Input should be 'NONE' or 'REQUIRED' [type=enum, input_value='PASSIVE', input_type=str]
    For further information visit https://errors.pydantic.dev/2.10/v/enum

[prabhu]

Thank you for reporting this! The continue-on-error flag was masking the issue. Have started the workflow with 6.2.3. Will keep an eye over the next few days as well.

However, please consider maintaining your own vdb workflows and databases.