| { |
| "task_id": "nvd_001", |
| "domain": "NVD", |
| "autonomy_type": "ordered table", |
| "instruction": "我们在清理一批旧 SBOM 匹配规则，其中有些规则仍把 Apache Tomcat 9.0.0 发布前的 milestone 版本写成 9.0.0.Mx这种旧版 CPE 形式；现在需要确认哪些 milestone 版本同时出现在 CVE-2016-5018、CVE-2016-6794、CVE-2016-6796 和 CVE-2016-6797 这四个 CVE 的 NVD 当前受影响产品版本范围中，并且能在 NVD 历史记录里看到从 m1、m2 这类旧 CPE 写法改为 milestone1、milestone2 这类完整 CPE 写法的记录。请从 Apache Tomcat 9.0.0 的 milestone 版本入手，逐一核对这四个 CVE 在 NVD 当前列出的受影响产品版本范围，只保留同时被四个 CVE 覆盖的 milestone 版本；再查看相应的 NVD 历史记录，确认是否存在旧 CPE 写法到完整 CPE 写法的变更，并记录该变更时间。筛选时请排除只由其他 Tomcat 9.0.0 发布前版本问题带入的 milestone，也不要纳入 Tomcat 6、7、8、8.5 或任何非 Tomcat 产品。最后，请按 milestone 编号的数值升序输出多行有序表，列为 milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd。", |
| "start_url": "https://nvd.nist.gov/vuln/search#/nvd/home?resultType=records", |
| "output_format": "最后，请按 milestone 编号的数值升序输出多行有序表，列为 milestone | legacy_cpe | current_cpe | required_cves | remap_time_nvd。", |
| "oracle_output_cardinality": 3, |
| "oracle_answer": "CVE:2018-7543|1.2.32|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2018-17207|1.2.42|lite|Reanalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02,CVE:2020-11738|1.3.28|lite+pro|ModifiedAnalysis@2021-10-18|snapcreek->awesomemotive@2026-02-02", |
| "metadata": { |
| "State-Gated Retrieval": [ |
| "只保留当前产品线属于 awesomemotive:duplicator、且在 deprecated 旧厂商链中能回溯到 snapcreek:duplicator 的 Duplicator 相关 CVE。", |
| "每个候选 CVE 都必须在 Change History 中同时满足：Initial Analysis 还不是 lite/lite+pro；后续在 2021-10-18 的 NIST 分析事件里第一次改到 lite 或 lite+pro；并在 2026-02-02 发生 snapcreek -> awesomemotive 的 vendor remap。", |
| "最终输出只保留满足上述三重条件的 CVE 行。" |
| ], |
| "dependency_type": "Data + Control", |
| "intra_chain": true, |
| "inter_chain": true, |
| "data_dependency": [ |
| "NVD product/CPE search pages yield the current awesomemotive:duplicator family and the deprecated snapcreek:duplicator lineage", |
| "each target CVE detail page and Change History yield the Initial Analysis state, the first lite/lite+pro analysis event, and the 2026-02-02 vendor-remap event", |
| "final rows are produced only after candidate CVEs are intersected on both snapcreek -> awesomemotive migration and later introduction of lite/lite+pro in NIST analysis history" |
| ], |
| "control_dependency": [ |
| "the search must include the deprecated snapcreek lineage rather than only the current product state", |
| "vendor migration alone is insufficient until detail-level history confirms that lite/lite+pro was introduced after Initial Analysis", |
| "candidate CVEs must be filtered against the full change-history chronology, excluding any whose Initial Analysis already contained lite" |
| ], |
| "freeze": { |
| "historical_window": "Duplicator CVEs published from 2018-01-01 through 2024-12-31, evaluated against NVD analysis history up to the 2026-02-02 snapcreek -> awesomemotive vendor-remap events" |
| }, |
| "answer_type": "multi-row ordered table" |
| }, |
| "rubric": { |
| "inclusion_conditions": [ |
| "只保留当前产品线属于 awesomemotive:duplicator、且在 deprecated 旧厂商链中能回溯到 snapcreek:duplicator 的 Duplicator 相关 CVE。", |
| "每个候选 CVE 都必须在 Change History 中同时满足：Initial Analysis 还不是 lite/lite+pro；后续在 2021-10-18 的 NIST 分析事件里第一次改到 lite 或 lite+pro；并在 2026-02-02 发生 snapcreek -> awesomemotive 的 vendor remap。", |
| "最终输出只保留满足上述三重条件的 CVE 行。" |
| ], |
| "exclusion_conditions": [ |
| "排除只看 current description 或 current product state、没有回退到 deprecated snapcreek 链和 Change History 的结果。", |
| "排除 Initial Analysis 就已经是 lite/lite+pro 的 CVE。", |
| "排除没有 2026-02-02 vendor remap、或不属于 Duplicator 产品线的记录。" |
| ], |
| "normalization": { |
| "field_separator": "|", |
| "record_separator": ",", |
| "schema_note": "the current source docx rubric, evidence, and oracle answer use a Duplicator CVE rowset, even though the instruction/output_format text still describes a Tomcat milestone task; normalization therefore follows the checked oracle row schema rather than the stale milestone wording", |
| "schema": [ |
| "CVE", |
| "lite_upper_version", |
| "lite_vs_lite+pro", |
| "analysis_event@date", |
| "snapcreek_to_awesomemotive@date" |
| ], |
| "CVE": "emit the identifier in the canonical `CVE:YYYY-NNNN` form used by the oracle", |
| "lite_vs_lite+pro": "emit `lite` or `lite+pro` exactly", |
| "analysis_event@date": "emit `Reanalysis@YYYY-MM-DD` or `ModifiedAnalysis@YYYY-MM-DD` exactly as supported by the source record", |
| "snapcreek_to_awesomemotive@date": "emit the ownership-transfer event as `snapcreek->awesomemotive@YYYY-MM-DD`", |
| "sorting_or_selection": { |
| "primary": "NVD published date ascending", |
| "secondary": "CVE ascending" |
| } |
| } |
| } |
| } |
|
|
