Skip to content

CVE_MAX_ALLOWABLE_CVE_YEAR is overly restrictive for most uses #57

@hkong-mitre

Description

@hkong-mitre

There is a check for CVE IDs to be restricted by the environment variable CVE_MAX_ALLOWABLE_CVE_YEAR. This has proven to be too restrictive for most uses since that rule is already checked in CVE REST Services, and keeping it in cve-core introduces a synchronization vulnerability among services.

I suggest changing the code to default to allowing any year, and only check the CVE_MAX_ALLOWABLE_CVE_YEAR in use cases that require it (e.g., an admin app or a verification service).

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