Skip to content

VEX fails on null key #279

@txdvse

Description

@txdvse

Overview

VEX feature fails and returns a 500 internal server error for certain SBOMs. This happens when one of the components has a null value key when generating VEX data.

Error occurs specifically in VEXController.java on line 80.

Acceptance Criteria

  • Prevent null keys from appearing before retrieving VEX data

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions