BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2021
CVE-2020-14343High confidence

n/a PyYAML — Improper Input Validation

Unknown · PyYAML

9.8CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 5.98% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Unknown PyYAML and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

7 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainpy3-yamlVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.5.4-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainpy3-yamlVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.5.4-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainpy3-yamlVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.5.4-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcepyyamlVendor fix publishedDebian records a fixed source-package version for this release.5.3.1-4Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcepyyamlVendor fix publishedDebian records a fixed source-package version for this release.5.3.1-4Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcepyyamlVendor fix publishedDebian records a fixed source-package version for this release.5.3.1-4Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcepyyamlVendor fix publishedDebian records a fixed source-package version for this release.5.3.1-4Debian Security Tracker ↗Source updated 6 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2020-14343 · CSAF 2.0 · revision 46 · interimSUSE Product Security TeamCVE-2020-14343
18 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • python-PyYAML as component of HPE Helion OpenStack Cloud 8
  • python-PyYAML as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • python3-PyYAML as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • python-PyYAML as component of SUSE Linux Enterprise Server 12 SP4
  • python3-PyYAML as component of SUSE Linux Enterprise Server 12 SP4
  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
Summary
A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2021-0216

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.

What

A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

A vulnerability was discovered in the PyYAML library in versions before 5.4, where it is susceptible to arbitrary code execution when it processes untrusted YAML files through the full_load method or with the FullLoader loader. Applications that use the library to process untrusted input may be vulnerable to this flaw. This flaw allows an attacker to execute arbitrary code on the system by abusing the python/object/new constructor. This flaw is due to an incomplete fix for CVE-2020-1747.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Input Validation → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-20
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2023-1032Oracle PeopleSoft: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle PeopleSoft ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2022-0721Red Hat Enterprise Linux: Mehrere Schwachstellen

Ein entfernter, anonymer, authentifizierter oder lokaler Angreifer kann mehrere Schwachstellen in Red Hat Enterprise Linux ausnutzen, um beliebigen Programmcode auszuführen und einen Denial of Service Zustand herzustellen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20210210Security Bulletin 10 Feb 2021

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 10 Feb 2021, published on 10 February 2021. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0395Multiples vulnérabilités dans les produits IBM

org/CVERecord?id=CVE-2019-20907 Référence CVE CVE-2019-20916 https://www.cve.org/CVERecord?id=CVE-2019-20916 Référence CVE CVE-2019-7164 https://www.cve.org/CVERecord?id=CVE-2019-7164 Référence CVE CVE-2019-7548 https://www.cve.org/CVERecord?id=CVE-2019-7548 Référence CVE CVE-2019-9636 https://www.cve.org/CVERecord?id=CVE-2019-9636 Référence CVE CVE-2019-9740 https://www.cve.org/CVERecord?id=CVE-2019-9740 Référence CVE CVE-2019-9947 https://www.cve.org/CVERecord?id=CVE-2019-9947 Référence CVE CVE-2019-9948 https://www.cve.org/CVERecord?id=CVE-2019-9948 Référence CVE CVE-2020-10735 https://www.cve.org/CVERecord?id=CVE-2020-10735 Référence CVE CVE-2020-14343 https://www.cve.org/CVERecord?id=CVE-2020-14343 Référence CVE CVE-2020-14422 https://www.cve.org/CVERecord?id=CVE-2020-14422 Référence CVE CVE-2020-1747 https://www.cve.org/CVERecord?id=CVE-2020-1747 Référence CVE CVE-2020-26116 https://www.cve.org/CVERecord?id=CVE-2020-26116 Référence CVE CVE-2020-26137 https://www.cve.org/CVERecord?id=CVE-2020-26137 Référence CVE CVE-2020-27619 https://www.cve.org/CVERecord?id=CVE-2020-27619 Référence CVE CVE-2020-27783 https://www.cve.org/CVERecord?id=CVE-2020-27783 Référence CVE CVE-2020-28493 https://www.cve.org/CVERecord?id=CVE-2020-28493 Référence CVE CVE-2020-8492 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0297Multiples vulnérabilités dans Juniper

id=CVE-2018-1000215 Référence CVE CVE-2018-1000654 https://www.cve.org/CVERecord?id=CVE-2018-1000654 Référence CVE CVE-2018-20225 https://www.cve.org/CVERecord?id=CVE-2018-20225 Référence CVE CVE-2018-20482 https://www.cve.org/CVERecord?id=CVE-2018-20482 Référence CVE CVE-2018-7738 https://www.cve.org/CVERecord?id=CVE-2018-7738 Référence CVE CVE-2019-17041 https://www.cve.org/CVERecord?id=CVE-2019-17041 Référence CVE CVE-2019-17042 https://www.cve.org/CVERecord?id=CVE-2019-17042 Référence CVE CVE-2019-18276 https://www.cve.org/CVERecord?id=CVE-2019-18276 Référence CVE CVE-2019-9923 https://www.cve.org/CVERecord?id=CVE-2019-9923 Référence CVE CVE-2020-14343 https://www.cve.org/CVERecord?id=CVE-2020-14343 Référence CVE CVE-2020-1747 https://www.cve.org/CVERecord?id=CVE-2020-1747 Référence CVE CVE-2020-19185 https://www.cve.org/CVERecord?id=CVE-2020-19185 Référence CVE CVE-2020-19186 https://www.cve.org/CVERecord?id=CVE-2020-19186 Référence CVE CVE-2020-19187 https://www.cve.org/CVERecord?id=CVE-2020-19187 Référence CVE CVE-2020-19188 https://www.cve.org/CVERecord?id=CVE-2020-19188 Référence CVE CVE-2020-19189 https://www.cve.org/CVERecord?id=CVE-2020-19189 Référence CVE CVE-2020-19190 https://www.cve.org/CVERecord?id=CVE-2020-19190 Référence CVE CVE-2020-22916 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0325Multiples vulnérabilités dans les produits Oracle

Oracle Virtualization versions 7.0.x antérieures à 7.0.8 Oracle WebLogic Server versions 12.2.1.3.0, 12.2.1.4.0, 14.1.1.0.0 Résumé De multiples vulnérabilités ont été découvertes dans les produits Oracle. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et un contournement de la politique de sécurité. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Oracle cpuapr2023 du 18 avril 2023 https://www.oracle.com/security-alerts/cpuapr2023.html Référence CVE CVE-2020-14343 https://www.cve.org/CVERecord?id=CVE-2020-14343 Référence CVE CVE-2020-25638 https://www.cve.org/CVERecord?id=CVE-2020-25638 Référence CVE CVE-2020-6950 https://www.cve.org/CVERecord?id=CVE-2020-6950 Référence CVE CVE-2021-22569 https://www.cve.org/CVERecord?id=CVE-2021-22569 Référence CVE CVE-2021-31684 https://www.cve.org/CVERecord?id=CVE-2021-31684 Référence CVE CVE-2021-36090 https://www.cve.org/CVERecord?id=CVE-2021-36090 Référence CVE CVE-2021-37533 https://www.cve.org/CVERecord?id=CVE-2021-37533 Référence CVE CVE-2022-1471 https://www.cve.org/CVERecord?id=CVE-2022-1471 Référence CVE CVE-2022-31160 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-650Multiples vulnérabilités dans les produits Juniper

d?id=CVE-2020-11655 Référence CVE CVE-2020-11656 https://www.cve.org/CVERecord?id=CVE-2020-11656 Référence CVE CVE-2020-12049 https://www.cve.org/CVERecord?id=CVE-2020-12049 Référence CVE CVE-2020-13434 https://www.cve.org/CVERecord?id=CVE-2020-13434 Référence CVE CVE-2020-13435 https://www.cve.org/CVERecord?id=CVE-2020-13435 Référence CVE CVE-2020-13630 https://www.cve.org/CVERecord?id=CVE-2020-13630 Référence CVE CVE-2020-13631 https://www.cve.org/CVERecord?id=CVE-2020-13631 Référence CVE CVE-2020-13632 https://www.cve.org/CVERecord?id=CVE-2020-13632 Référence CVE CVE-2020-13871 https://www.cve.org/CVERecord?id=CVE-2020-13871 Référence CVE CVE-2020-14343 https://www.cve.org/CVERecord?id=CVE-2020-14343 Référence CVE CVE-2020-14363 https://www.cve.org/CVERecord?id=CVE-2020-14363 Référence CVE CVE-2020-14556 https://www.cve.org/CVERecord?id=CVE-2020-14556 Référence CVE CVE-2020-14577 https://www.cve.org/CVERecord?id=CVE-2020-14577 Référence CVE CVE-2020-14578 https://www.cve.org/CVERecord?id=CVE-2020-14578 Référence CVE CVE-2020-14579 https://www.cve.org/CVERecord?id=CVE-2020-14579 Référence CVE CVE-2020-14583 https://www.cve.org/CVERecord?id=CVE-2020-14583 Référence CVE CVE-2020-14593 https://www.cve.org/CVERecord?id=CVE-2020-14593 Référence CVE CVE-2020-14621 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-278Multiples vulnérabilités dans IBM Spectrum discover

6889 Bulletin de sécurité IBM 6568675 du 31 mars 2022 https://www.ibm.com/support/pages/node/6568675 Référence CVE CVE-2013-7459 https://www.cve.org/CVERecord?id=CVE-2013-7459 Référence CVE CVE-2018-6594 https://www.cve.org/CVERecord?id=CVE-2018-6594 Référence CVE CVE-2019-19919 https://www.cve.org/CVERecord?id=CVE-2019-19919 Référence CVE CVE-2019-20477 https://www.cve.org/CVERecord?id=CVE-2019-20477 Référence CVE CVE-2019-20920 https://www.cve.org/CVERecord?id=CVE-2019-20920 Référence CVE CVE-2019-20922 https://www.cve.org/CVERecord?id=CVE-2019-20922 Référence CVE CVE-2020-13822 https://www.cve.org/CVERecord?id=CVE-2020-13822 Référence CVE CVE-2020-14343 https://www.cve.org/CVERecord?id=CVE-2020-14343 Référence CVE CVE-2020-15366 https://www.cve.org/CVERecord?id=CVE-2020-15366 Référence CVE CVE-2020-1747 https://www.cve.org/CVERecord?id=CVE-2020-1747 Référence CVE CVE-2020-28498 https://www.cve.org/CVERecord?id=CVE-2020-28498 Référence CVE CVE-2020-7608 https://www.cve.org/CVERecord?id=CVE-2020-7608 Référence CVE CVE-2020-7660 https://www.cve.org/CVERecord?id=CVE-2020-7660 Référence CVE CVE-2020-7699 https://www.cve.org/CVERecord?id=CVE-2020-7699 Référence CVE CVE-2020-7720 https://www.cve.org/CVERecord?id=CVE-2020-7720 Référence CVE CVE-2020-7751 https://www.cve.org/CVERecord?id=CVE-2020-77

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2020-016031PyYAML library における入力確認に関する脆弱性

PyYAML library には、入力確認に関する脆弱性が存在します。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-016924pytorch-lightning における信頼できないデータのデシリアライゼーションに関する脆弱性

pytorch-lightning には、信頼できないデータのデシリアライゼーションに関する脆弱性が存在します。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-5484Juniper 제품군 보안 업데이트 권고

#### Juniper 제품군 보안 업데이트 권고 2022.01.14 ##### □ 개요 o Juniper Networks社는 자사 제품에 대해 다수의 취약점을 해결한 보안 업데이트를 공지 o 영향받는 버전을 사용 중인 이용자는 최신 버전으로 업데이트 권고 ##### □ 설명 [1] o Junos OS에서 발생하는 정보노출 취약점(CVE-2022-22168) 등 32개 o Junos Space에서 발생하는 임의코드실행 취약점(CVE-2021-31535) 등 61개 o MX Series 및 SRX Series에서 발생하는 서비스거부 취약점(CVE-2022-22175) 등 3개 o Junos Fusion에서 발생하는 서비스거부 취약점(CVE-2022-22154) o Contrail Cloud에서 발생하는 버퍼오버플로우 취약점(CVE-2019-5482) 등 13개 o Contrail Networking에서 발생하는 임의코드실행 취약점(CVE-2020-14343) 등 11개 o Contrail Service Orchestration에서 발생하는 정보노출 취약점(CVE-2022-22152) ##### □ 영향을 받는 시스템 o 참고사이트에 명시되어 있는 ‘PRODUCT AFFECTED’을 통해 취약한 제품 확인 ##### □ 해결 방안 o 취약한 Juniper 소프트웨어가 설치된 Juniper 장비의 운영자는 해당사이트에 명시되어 있는 ‘SOLUTION’ 내용을 확인하여 패치를 적용하거나 ‘WORKAROUND’ 내용을 확인하여 보안 설정 적용 ##### □ 기타 문의사항 o 한국인터넷진흥원 인터넷침해대응센터: 국번없이 118 [참고사이트] [1] https://kb.juniper.net/InfoCenter/index?page=content&channel=SECURITY_ADVISORIES ##### □ 작성 : 침해사고분석단 취약점분석팀

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 9 Feb 2021 · Last source change 4 Aug 2024, 12:39 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2021-0216
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    PyYAML 5.4 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    PyYAML 5.4 · Fixed: To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
    SUSE Product Security Team ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2020-14343 · cve.blacktree.nl