[security][HIGH] python3 3.12.12: 5 CVE require triage #3

Open
opened 2026-05-25 20:44:31 +03:00 by sbelikov · 0 comments
Owner

CVE triage request / Запрос на разбор CVE

Package / Пакет

  • Package: python3
  • Version: 3.12.12
  • EVR: 3.12.12-2
  • Category: -
  • Policy class: -
  • NiceOS policy class: -
  • Owner: -
  • Severity: HIGH
  • Max CVSS: 8.8
  • CVE count: 5
  • Included NiceOS statuses: needs_triage
  • Included match types: cpe-range

LLM recommendation / Рекомендация LLM

RU

Для пакета python3 3.12.12 найдены CVE-кандидаты по данным NVD/CPE: CVE-2020-1171, CVE-2020-1192, CVE-2020-17163, CVE-2024-49050, CVE-2025-49714. Требуется triage security-team.

Проверить применимость CVE к сборке НАЙС.ОС, сопоставить с upstream/vendor advisory, определить статус affected/fixed/not_affected и при необходимости подготовить обновление пакета.

Рекомендуемое действие: needs_triage

Подсказка по целевой версии: -

Проверки: Проверить сборку RPM, обновление пакета, совместимость зависимостей, service/CLI smoke tests и регрессионные сценарии по классу пакета.

Риски: Автоматическое совпадение NVD/CPE не является финальным вердиктом по НАЙС.ОС.

EN

NVD/CPE candidate CVEs were found for python3 3.12.12: CVE-2020-1171, CVE-2020-1192, CVE-2020-17163, CVE-2024-49050, CVE-2025-49714. Security-team triage is required.

Verify CVE applicability to the NiceOS build, compare with upstream/vendor advisories, set affected/fixed/not_affected status, and prepare a package update if required.

Recommended action: needs_triage

Target version hint: -

Tests: Run RPM build, package upgrade, dependency compatibility, service/CLI smoke tests, and package-class-specific regression tests.

Risks: An automatic NVD/CPE match is not the final NiceOS vulnerability verdict.

CVE candidates from NVD/CPE

CVE Severity CVSS Match Confidence NiceOS status Fixed in Existing issue Reason
CVE-2020-1171 HIGH 8.8 cpe-range 78 needs_triage package version is inside version range
CVE-2024-49050 HIGH 8.8 cpe-range 78 needs_triage package version is inside version range
CVE-2020-1192 HIGH 7.8 cpe-range 78 needs_triage package version is inside version range
CVE-2020-17163 HIGH 7.8 cpe-range 78 needs_triage package version is inside version range
CVE-2025-49714 HIGH 7.8 cpe-range 78 needs_triage package version is inside version range

Descriptions

CVE-2020-1171

A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads configuration files after opening a project, aka 'Visual Studio Code Python Extension Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-1192.

CVE-2024-49050

Visual Studio Code Python Extension Remote Code Execution Vulnerability

CVE-2020-1192

A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads workspace settings from a notebook file, aka 'Visual Studio Code Python Extension Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-1171.

CVE-2020-17163

Visual Studio Code Python Extension Remote Code Execution Vulnerability

CVE-2025-49714

Trust boundary violation in Visual Studio Code - Python extension allows an unauthorized attacker to execute code locally.

Scanner integration / Интеграция со сканером

This issue was generated from niceos_cve_matches after the SPEC/Forgejo evidence pass.
After real creation, this script writes forgejo_issue_open rows into niceos_cve_evidence and marks the selected CVE rows as issue_open, so the next scanner/creator run does not duplicate the issue.

Maintainer checklist

  • Verify whether each CVE applies to the NiceOS build.
  • Compare NVD data with upstream/vendor advisory.
  • Set final NiceOS status: affected, fixed, not_affected, false_positive, deferred, or not_in_cloud_image.
  • If affected, decide update/backport strategy according to package policy class.
  • Run package-class-specific build, upgrade and regression tests.
  • Add/update niceos_cve_triage entry.
  • Create NICE-SA advisory if a security update is shipped.

Machine metadata

{
  "cves": [
    "CVE-2020-1171",
    "CVE-2020-1192",
    "CVE-2020-17163",
    "CVE-2024-49050",
    "CVE-2025-49714"
  ],
  "fingerprint": "02ed6f7ddfa5cf08c277",
  "generated_at": "2026-05-25T17:44:31Z",
  "match_ids": [
    1714,
    1715,
    1716,
    1717,
    1718
  ],
  "match_types": [
    "cpe-range"
  ],
  "package": "python3",
  "prompt_version": "niceos_cve_issue_analysis_v2",
  "statuses": [
    "needs_triage"
  ],
  "tool": "niceos_cve_create_issues.py",
  "tool_version": "2.0",
  "version": "3.12.12"
}
<!-- niceos-cve-fingerprint: 02ed6f7ddfa5cf08c277 --> <!-- niceos-cve-package: python3 --> <!-- niceos-cve-cves: CVE-2020-1171, CVE-2020-1192, CVE-2020-17163, CVE-2024-49050, CVE-2025-49714 --> <!-- niceos-cve-source: niceos_cve_scan_packages_auto_cpe --> # CVE triage request / Запрос на разбор CVE ## Package / Пакет - Package: `python3` - Version: `3.12.12` - EVR: `3.12.12-2` - Category: `-` - Policy class: `-` - NiceOS policy class: `-` - Owner: `-` - Severity: `HIGH` - Max CVSS: `8.8` - CVE count: `5` - Included NiceOS statuses: `needs_triage` - Included match types: `cpe-range` ## LLM recommendation / Рекомендация LLM ### RU Для пакета python3 3.12.12 найдены CVE-кандидаты по данным NVD/CPE: CVE-2020-1171, CVE-2020-1192, CVE-2020-17163, CVE-2024-49050, CVE-2025-49714. Требуется triage security-team. Проверить применимость CVE к сборке НАЙС.ОС, сопоставить с upstream/vendor advisory, определить статус affected/fixed/not_affected и при необходимости подготовить обновление пакета. **Рекомендуемое действие:** `needs_triage` **Подсказка по целевой версии:** `-` **Проверки:** Проверить сборку RPM, обновление пакета, совместимость зависимостей, service/CLI smoke tests и регрессионные сценарии по классу пакета. **Риски:** Автоматическое совпадение NVD/CPE не является финальным вердиктом по НАЙС.ОС. ### EN NVD/CPE candidate CVEs were found for python3 3.12.12: CVE-2020-1171, CVE-2020-1192, CVE-2020-17163, CVE-2024-49050, CVE-2025-49714. Security-team triage is required. Verify CVE applicability to the NiceOS build, compare with upstream/vendor advisories, set affected/fixed/not_affected status, and prepare a package update if required. **Recommended action:** `needs_triage` **Target version hint:** `-` **Tests:** Run RPM build, package upgrade, dependency compatibility, service/CLI smoke tests, and package-class-specific regression tests. **Risks:** An automatic NVD/CPE match is not the final NiceOS vulnerability verdict. ## CVE candidates from NVD/CPE | CVE | Severity | CVSS | Match | Confidence | NiceOS status | Fixed in | Existing issue | Reason | |---|---|---:|---|---:|---|---|---|---| | CVE-2020-1171 | HIGH | 8.8 | cpe-range | 78 | needs_triage | | | package version is inside version range | | CVE-2024-49050 | HIGH | 8.8 | cpe-range | 78 | needs_triage | | | package version is inside version range | | CVE-2020-1192 | HIGH | 7.8 | cpe-range | 78 | needs_triage | | | package version is inside version range | | CVE-2020-17163 | HIGH | 7.8 | cpe-range | 78 | needs_triage | | | package version is inside version range | | CVE-2025-49714 | HIGH | 7.8 | cpe-range | 78 | needs_triage | | | package version is inside version range | ## Descriptions ### CVE-2020-1171 A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads configuration files after opening a project, aka 'Visual Studio Code Python Extension Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-1192. ### CVE-2024-49050 Visual Studio Code Python Extension Remote Code Execution Vulnerability ### CVE-2020-1192 A remote code execution vulnerability exists in Visual Studio Code when the Python extension loads workspace settings from a notebook file, aka 'Visual Studio Code Python Extension Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-1171. ### CVE-2020-17163 Visual Studio Code Python Extension Remote Code Execution Vulnerability ### CVE-2025-49714 Trust boundary violation in Visual Studio Code - Python extension allows an unauthorized attacker to execute code locally. ## Scanner integration / Интеграция со сканером This issue was generated from `niceos_cve_matches` after the SPEC/Forgejo evidence pass. After real creation, this script writes `forgejo_issue_open` rows into `niceos_cve_evidence` and marks the selected CVE rows as `issue_open`, so the next scanner/creator run does not duplicate the issue. ## Maintainer checklist - [ ] Verify whether each CVE applies to the NiceOS build. - [ ] Compare NVD data with upstream/vendor advisory. - [ ] Set final NiceOS status: `affected`, `fixed`, `not_affected`, `false_positive`, `deferred`, or `not_in_cloud_image`. - [ ] If affected, decide update/backport strategy according to package policy class. - [ ] Run package-class-specific build, upgrade and regression tests. - [ ] Add/update `niceos_cve_triage` entry. - [ ] Create `NICE-SA` advisory if a security update is shipped. ## Machine metadata ```json { "cves": [ "CVE-2020-1171", "CVE-2020-1192", "CVE-2020-17163", "CVE-2024-49050", "CVE-2025-49714" ], "fingerprint": "02ed6f7ddfa5cf08c277", "generated_at": "2026-05-25T17:44:31Z", "match_ids": [ 1714, 1715, 1716, 1717, 1718 ], "match_types": [ "cpe-range" ], "package": "python3", "prompt_version": "niceos_cve_issue_analysis_v2", "statuses": [ "needs_triage" ], "tool": "niceos_cve_create_issues.py", "tool_version": "2.0", "version": "3.12.12" } ```
Sign in to join this conversation.
No description provided.