BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2019
CVE-2019-10744High confidence

Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution

Snyk · lodash

Official source article: Red Hat RHSA-2019:3024 ↗. Check the applicable product and release in the original source.

9.1CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path and a public exploit reference; 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.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 5.01% 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.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Snyk lodash 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

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

4 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
Debian trixietrixie · sourcenode-lodashVendor fix publishedDebian records a fixed source-package version for this release.4.17.15+dfsg-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcenode-lodashVendor fix publishedDebian records a fixed source-package version for this release.4.17.15+dfsg-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcenode-lodashVendor fix publishedDebian records a fixed source-package version for this release.4.17.15+dfsg-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcenode-lodashVendor fix publishedDebian records a fixed source-package version for this release.4.17.15+dfsg-1Debian Security Tracker ↗Source updated 6 Oct 2026
Open-source package ranges10 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
RubyGemslodash-railsECOSYSTEM: introduced 0; fixed 4.17.124.17.12OSV record ↗aggregator derived · 10 Sep 2026
npmlodash< 4.17.124.17.12GitHub advisory ↗github reviewed aggregator · 12 Aug 2025
npmlodashSEMVER: introduced 0; fixed 4.17.124.17.12OSV record ↗aggregator derived · 10 Sep 2026
npmlodash-amd< 4.17.134.17.13GitHub advisory ↗github reviewed aggregator · 12 Aug 2025
npmlodash-amdSEMVER: introduced 0; fixed 4.17.134.17.13OSV record ↗aggregator derived · 10 Sep 2026
npmlodash-es< 4.17.144.17.14GitHub advisory ↗github reviewed aggregator · 12 Aug 2025
npmlodash-esSEMVER: introduced 0; fixed 4.17.144.17.14OSV record ↗aggregator derived · 10 Sep 2026
npmlodash.defaultsdeep< 4.6.14.6.1GitHub advisory ↗github reviewed aggregator · 12 Aug 2025
npmlodash.defaultsdeepSEMVER: introduced 0; fixed 4.6.14.6.1OSV record ↗aggregator derived · 10 Sep 2026
rubygemslodash-rails< 4.17.124.17.12GitHub advisory ↗github reviewed aggregator · 12 Aug 2025
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-2019-0597

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 and a public exploit reference; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.

What

Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.

Why

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Versions of lodash lower than 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.

Why

The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') → cause the confidentiality, integrity or availability impact described by the vendor
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-1321 ↗

CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution'). The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.

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:N/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.CNoneConfidentiality impact: No direct loss is represented by this metric.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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-1321Public exploit reference
A

Official authority intelligence

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

BSI · German · WID-SEC-2024-0597SAP Security Patch Day – März 2024

Ein Angreifer kann mehrere Schwachstellen in der SAP-Software ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen oder Cross-Site-Scripting (XSS)-Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2023-1350Splunk Splunk Enterprise: Mehrere Schwachstellen in Komponenten von Drittanbietern

Ein Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise in diversen Komponenten von Drittanbietern ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-3184Elasticsearch/Kibana: Mehrere Schwachstellen

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Elasticsearch und Kibana ausnutzen, um beliebigen Programmcode mit den Rechten des Dienstes auszuführen, Sicherheitsmechanismen zu umgehen und Informationen offenzulegen.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0756Multiples vulnérabilités dans les produits VMware

.cve.org/CVERecord?id=CVE-2018-3182 Référence CVE CVE-2018-3186 https://www.cve.org/CVERecord?id=CVE-2018-3186 Référence CVE CVE-2018-3195 https://www.cve.org/CVERecord?id=CVE-2018-3195 Référence CVE CVE-2018-3203 https://www.cve.org/CVERecord?id=CVE-2018-3203 Référence CVE CVE-2018-3212 https://www.cve.org/CVERecord?id=CVE-2018-3212 Référence CVE CVE-2018-3279 https://www.cve.org/CVERecord?id=CVE-2018-3279 Référence CVE CVE-2018-3280 https://www.cve.org/CVERecord?id=CVE-2018-3280 Référence CVE CVE-2018-3285 https://www.cve.org/CVERecord?id=CVE-2018-3285 Référence CVE CVE-2018-3286 https://www.cve.org/CVERecord?id=CVE-2018-3286 Référence CVE CVE-2019-10744 https://www.cve.org/CVERecord?id=CVE-2019-10744 Référence CVE CVE-2019-10782 https://www.cve.org/CVERecord?id=CVE-2019-10782 Référence CVE CVE-2019-18276 https://www.cve.org/CVERecord?id=CVE-2019-18276 Référence CVE CVE-2019-2436 https://www.cve.org/CVERecord?id=CVE-2019-2436 Référence CVE CVE-2019-2494 https://www.cve.org/CVERecord?id=CVE-2019-2494 Référence CVE CVE-2019-2495 https://www.cve.org/CVERecord?id=CVE-2019-2495 Référence CVE CVE-2019-25013 https://www.cve.org/CVERecord?id=CVE-2019-25013 Référence CVE CVE-2019-2502 https://www.cve.org/CVERecord?id=CVE-2019-2502 Référence CVE CVE-2019-2513 https://www.cve.org/CVERecord?id=CVE-2019-

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0209Multiples vulnérabilités dans les produits SAP

De multiples vulnérabilités ont été découvertes dans les produits SAP . Certaines d'entre elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données et une exécution de code arbitraire à distance et un déni de service à distance.

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

y.splunk.com/advisories/SVD-2023-0611 Bulletin de sécurité Splunk SVD-2023-0612 du 01 juin 2023 https://advisory.splunk.com/advisories/SVD-2023-0612 Bulletin de sécurité Splunk SVD-2023-0613 du 01 juin 2023 https://advisory.splunk.com/advisories/SVD-2023-0613 Bulletin de sécurité Splunk SVD-2023-0614 du 01 juin 2023 https://advisory.splunk.com/advisories/SVD-2023-0614 Bulletin de sécurité Splunk SVD-2023-0615 du 01 juin 2023 https://advisory.splunk.com/advisories/SVD-2023-0615 Référence CVE CVE-2017-16042 https://www.cve.org/CVERecord?id=CVE-2017-16042 Référence CVE CVE-2018-25032 https://www.cve.org/CVERecord?id=CVE-2018-25032 Référence CVE CVE-2019-10744 https://www.cve.org/CVERecord?id=CVE-2019-10744 Référence CVE CVE-2019-10746 https://www.cve.org/CVERecord?id=CVE-2019-10746 Référence CVE CVE-2019-20149 https://www.cve.org/CVERecord?id=CVE-2019-20149 Référence CVE CVE-2019-8331 https://www.cve.org/CVERecord?id=CVE-2019-8331 Référence CVE CVE-2020-13822 https://www.cve.org/CVERecord?id=CVE-2020-13822 Référence CVE CVE-2020-15138 https://www.cve.org/CVERecord?id=CVE-2020-15138 Référence CVE CVE-2020-28469 https://www.cve.org/CVERecord?id=CVE-2020-28469 Référence CVE CVE-2020-7662 https://www.cve.org/CVERecord?id=CVE-2020-7662 Référence CVE CVE-2020-7753 https://www.cve.org/CVERecord?id=CVE-2

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

d?id=CVE-2018-16487 Référence CVE CVE-2018-20406 https://www.cve.org/CVERecord?id=CVE-2018-20406 Référence CVE CVE-2018-20852 https://www.cve.org/CVERecord?id=CVE-2018-20852 Référence CVE CVE-2018-25031 https://www.cve.org/CVERecord?id=CVE-2018-25031 Référence CVE CVE-2018-3721 https://www.cve.org/CVERecord?id=CVE-2018-3721 Référence CVE CVE-2019-0205 https://www.cve.org/CVERecord?id=CVE-2019-0205 Référence CVE CVE-2019-1010266 https://www.cve.org/CVERecord?id=CVE-2019-1010266 Référence CVE CVE-2019-10172 https://www.cve.org/CVERecord?id=CVE-2019-10172 Référence CVE CVE-2019-10202 https://www.cve.org/CVERecord?id=CVE-2019-10202 Référence CVE CVE-2019-10744 https://www.cve.org/CVERecord?id=CVE-2019-10744 Référence CVE CVE-2019-11358 https://www.cve.org/CVERecord?id=CVE-2019-11358 Référence CVE CVE-2019-16935 https://www.cve.org/CVERecord?id=CVE-2019-16935 Référence CVE CVE-2019-18348 https://www.cve.org/CVERecord?id=CVE-2019-18348 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-2020-11022 https://www.cve.org/CVERecord?id=CVE-2020-11022 Référence CVE CVE-2020-11023 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-924Multiples vulnérabilités dans IBM QRadar

tion 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é IBM 6827633 du 17 octobre 2022 https://www.ibm.com/support/pages/node/6827633 Bulletin de sécurité IBM 6830017 du 17 octobre 2022 https://www.ibm.com/support/pages/node/6830017 Référence CVE CVE-2018-16487 https://www.cve.org/CVERecord?id=CVE-2018-16487 Référence CVE CVE-2018-25031 https://www.cve.org/CVERecord?id=CVE-2018-25031 Référence CVE CVE-2018-3721 https://www.cve.org/CVERecord?id=CVE-2018-3721 Référence CVE CVE-2019-1010266 https://www.cve.org/CVERecord?id=CVE-2019-1010266 Référence CVE CVE-2019-10744 https://www.cve.org/CVERecord?id=CVE-2019-10744 Référence CVE CVE-2019-11358 https://www.cve.org/CVERecord?id=CVE-2019-11358 Référence CVE CVE-2020-11022 https://www.cve.org/CVERecord?id=CVE-2020-11022 Référence CVE CVE-2020-11023 https://www.cve.org/CVERecord?id=CVE-2020-11023 Référence CVE CVE-2020-28469 https://www.cve.org/CVERecord?id=CVE-2020-28469 Référence CVE CVE-2020-7598 https://www.cve.org/CVERecord?id=CVE-2020-7598 Référence CVE CVE-2020-7788 https://www.cve.org/CVERecord?id=CVE-2020-7788 Référence CVE CVE-2020-8203 https://www.cve.org/CVERecord?id=CVE-2020-8203 Référence CVE CVE-2021-22959 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-1025Multiples vulnérabilités dans IBM QRadar

De multiples vulnérabilités ont été découvertes dans IBM QRadar. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance, un contournement de la politique de sécurité et une atteinte à l'intégrité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2021-AVI-951Multiples vulnérabilités dans le noyau Linux de RedHat

SA-2021:5130 du 14 décembre 2021 https://access.redhat.com/errata/RHSA-2021:5130 Bulletin de sécurité RedHat RHSA-2021:5132 du 14 décembre 2021 https://access.redhat.com/errata/RHSA-2021:5132 Bulletin de sécurité RedHat RHSA-2021:5133 du 14 décembre 2021 https://access.redhat.com/errata/RHSA-2021:5133 Bulletin de sécurité RedHat RHSA-2021:5134 du 14 décembre 2021 https://access.redhat.com/errata/RHSA-2021:5134 Bulletin de sécurité RedHat RHSA-2021:5138 du 14 décembre 2021 https://access.redhat.com/errata/RHSA-2021:5138 Bulletin de sécurité RedHat RHSA-2021:5101 du 14 décembre 2021 https://access.redhat.com/errata/RHBA-2021:5101 Référence CVE CVE-2019-10744 https://www.cve.org/CVERecord?id=CVE-2019-10744 Référence CVE CVE-2019-12415 https://www.cve.org/CVERecord?id=CVE-2019-12415 Référence CVE CVE-2020-11987 https://www.cve.org/CVERecord?id=CVE-2020-11987 Référence CVE CVE-2020-11988 https://www.cve.org/CVERecord?id=CVE-2020-11988 Référence CVE CVE-2020-13943 https://www.cve.org/CVERecord?id=CVE-2020-13943 Référence CVE CVE-2020-13949 https://www.cve.org/CVERecord?id=CVE-2020-13949 Référence CVE CVE-2020-15522 https://www.cve.org/CVERecord?id=CVE-2020-15522 Référence CVE CVE-2020-17521 https://www.cve.org/CVERecord?id=CVE-2020-17521 Référence CVE CVE-2020-17527 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2019-007275lodash におけるオブジェクトプロトタイプ属性の不適切に制御された変更に関する脆弱性

lodash には、オブジェクトプロトタイプ属性の不適切に制御された変更に関する脆弱性が存在します。

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
lodash: All versions prior to 4.17.12
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.
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
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 25 Jul 2019 · Last source change 4 Aug 2024, 22:32 UTC · CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

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-09-01
European sourceENISA EUVD · EUVD-2019-0597
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. ENISA EUVD mappingEUVD-2019-0597 was added to the official ENISA EUVD mapping for this CVE.
    Before
    not recorded
    After
    {"euvdId":"EUVD-2019-0597"}
    ENISA EUVD ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added patch: oracle.com/cpujan2021.html; added patch: oracle.com/cpuoct2020.html; removed vendor advisory: access.redhat.com/RHSA-2019:3024; 1 further additions.
    Before
    vendor advisory: access.redhat.com/RHSA-2019:3024
    After
    patch: oracle.com/cpujan2021.html · patch: oracle.com/cpuoct2020.html · remediation: oracle.com/cpuoct2020.html
    oracle.com ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    All versions prior to 4.17.12 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    All versions prior to 4.17.12 · 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.
    CNA ↗
  4. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    oracle.com ↗
  5. Public exploit evidencePublic exploit evidence changed from No public exploit to Public exploit reference.
    Before
    No public exploit
    After
    Public exploit reference
    snyk.io ↗
  6. SeveritySeverity changed from Unknown to Critical.
    Before
    Unknown
    After
    Critical
    NIST NVD ↗
  7. CVSS scoreCVSS score changed from not recorded to 9.1 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H).
    Before
    not recorded
    After
    9.1 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H)
    NIST NVD ↗
  8. Catalogue recordCVE added to the BlackTree catalogue.
    CNA ↗
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-2019-10744 · cve.blacktree.nl