Security readout for executives and security teams
Plain-English summary
CVE-2021-23338 affects the Python package qlib. Its CLI workflow feature used unsafe YAML loading, so a trusted user with access to run that workflow could cause serious confidentiality, integrity, or availability impact if malicious YAML is processed.
Executive priority
Treat this as a targeted dependency risk, not an internet-wide emergency. Prioritize teams using qlib workflow automation with externally influenced YAML or privileged execution contexts.
Technical view
The issue is deserialization of untrusted data in qlib's CLI workflow function due to an unsafe YAML load function. The CVSS vector indicates network reachability, high attack complexity, high privileges required, no user interaction, unchanged scope, and high C/I/A impact.
Likely exposure
Exposure is most likely in Python environments that install qlib and invoke its CLI workflow processing, especially where YAML workflow input can come from users, partners, CI jobs, or automation.
Exploitation context
The source bundle lists proof-of-concept maturity in CVSS, but KEV is false and no cited source here confirms active exploitation. High privileges and high complexity reduce broad opportunistic risk.
Researcher notes
Evidence is limited to the CVE summary, Snyk reference, and huntr pull request link in the bundle. Do not assume a fixed version, exploit-in-the-wild status, or broader product impact without vendor confirmation.
Mitigation direction
- Inventory Python environments for qlib and confirm whether the CLI workflow function is used.
- Do not process untrusted YAML through qlib CLI workflow until vendor guidance is reviewed.
- Review Snyk and upstream huntr discussion for any fixed release or workaround before upgrading.
- Restrict access to systems or jobs that can invoke qlib workflow processing.
- Replace qlib where continued use cannot be justified or safely constrained.
Validation and detection
- Search dependency manifests and runtime images for qlib.
- Identify automation paths that feed YAML to qlib workflow.
- Confirm whether YAML inputs are user-supplied, partner-supplied, or internally generated.
- Record installed version and compare it with current advisory guidance.
- Check job history for unexpected qlib workflow invocations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-23338 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:U/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:U/RC:C0.75.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.6MediumVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:U/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- https://snyk.io/vuln/SNYK-PYTHON-QLIB-1054635CVE reference · x_refsource_MISC
- https://github.com/418sec/huntr/pull/1329CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
