{"api_version":"v1","generated_at":"2026-10-08T15:35:00+00:00","product":{"cve_count":15,"evidence_gap_note":"Official registry publication history is linked, but a publisher support or retirement boundary has not been established.","id":"security:cve-huawei-technologies-uma-33b51fe9d8e0","lifecycle_state":"evidence_gap","linked_lifecycle_url":"https://lifecycle.blacktree.nl/libraries/npm/uma","name":"UMA","next_cursor":null,"observations":[{"affected":"V200R001C00","affected_versions_present":true,"cve_id":"CVE-2017-15329","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-15329","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-08-05T19:50:16.490Z","patch_url":"","primary_source":"","published":"2018-02-15T16:00:00.000Z"},{"affected":"V200R001 and V300R001","affected_versions_present":true,"cve_id":"CVE-2017-8130","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8130","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-16T20:31:32.805Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001 and V300R001","affected_versions_present":true,"cve_id":"CVE-2017-8129","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8129","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-17T01:11:30.305Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001 and V300R001","affected_versions_present":true,"cve_id":"CVE-2017-8128","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8128","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-17T01:41:17.091Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001","affected_versions_present":true,"cve_id":"CVE-2017-8127","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8127","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-16T18:38:18.173Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001","affected_versions_present":true,"cve_id":"CVE-2017-8126","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8126","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-17T02:53:18.489Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001 and V300R001","affected_versions_present":true,"cve_id":"CVE-2017-8125","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8125","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-17T02:11:20.755Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001","affected_versions_present":true,"cve_id":"CVE-2017-8124","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8124","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-16T19:05:42.567Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001","affected_versions_present":true,"cve_id":"CVE-2017-8123","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8123","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-17T02:51:47.251Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001","affected_versions_present":true,"cve_id":"CVE-2017-8122","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8122","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-16T20:32:07.760Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001","affected_versions_present":true,"cve_id":"CVE-2017-8121","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8121","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-17T00:51:56.733Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001 and V300R001","affected_versions_present":true,"cve_id":"CVE-2017-8120","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8120","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-16T17:19:03.398Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001 and V300R001","affected_versions_present":true,"cve_id":"CVE-2017-8119","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8119","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-17T02:26:42.084Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001 and V300R001","affected_versions_present":true,"cve_id":"CVE-2017-8118","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8118","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-16T23:10:49.836Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"},{"affected":"V200R001 and V300R001","affected_versions_present":true,"cve_id":"CVE-2017-8117","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-8117","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2024-09-17T00:06:02.713Z","patch_url":"","primary_source":"","published":"2017-11-22T19:00:00.000Z"}],"source_generated_at":"2026-10-08T06:18:52.353Z","vendor":"Huawei Technologies Co., Ltd."}}