{"api_version":"v1","generated_at":"2026-10-10T01:50:00+00:00","product":{"cve_count":15,"evidence_gap_note":"This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.","id":"security:cve-publisher-not-identified-hindu-matrimonial-script-3da6290f0607","lifecycle_state":"evidence_gap","linked_lifecycle_url":null,"name":"Hindu Matrimonial Script","next_cursor":null,"observations":[{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20081","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20081","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:16:03.094Z","patch_url":"","primary_source":"","published":"2022-06-21T06:06:07.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20080","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20080","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:16:12.251Z","patch_url":"","primary_source":"","published":"2022-06-21T06:06:05.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20079","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20079","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:16:22.852Z","patch_url":"","primary_source":"","published":"2022-06-21T06:06:03.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20078","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20078","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:16:31.347Z","patch_url":"","primary_source":"","published":"2022-06-21T06:06:00.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20077","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20077","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:16:46.878Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:58.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20076","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20076","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:16:53.850Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:56.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20075","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20075","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:17:02.523Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:55.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20074","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20074","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:17:13.745Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:53.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20073","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20073","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:17:23.805Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:51.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20072","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20072","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:17:34.948Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:49.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20071","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20071","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:17:47.678Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:47.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20070","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20070","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:17:59.199Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:45.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20069","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20069","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:18:10.809Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:43.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20068","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20068","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:18:21.329Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:42.000Z"},{"affected":"n/a","affected_versions_present":true,"cve_id":"CVE-2017-20067","cve_url":"https://cve.blacktree.nl/cve/CVE-2017-20067","fixed":"No fixed version is explicitly recorded in the structured CVE data.","last_modified":"2025-04-15T14:18:36.716Z","patch_url":"","primary_source":"","published":"2022-06-21T06:05:40.000Z"}],"source_generated_at":"2026-10-09T06:17:25.511Z","vendor":"Publisher not identified"}}