CVE-2020-7942 (GCVE-0-2020-7942)

Vulnerability from cvelistv5 – Published: 2020-02-19 20:52 – Updated: 2024-08-04 09:48
VLAI
Summary
Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node's catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19
Severity
6.5 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CWE
  • Arbitrary retrieval
Assigner
puppet CNA
CNA scorecard – unranked: 0 records in the last 180 days, 10 needed details
References
URL Tags
https://puppet.com/security/cve/CVE-2020-7942/ x_refsource_CONFIRM
Impacted products
Vendor Product Version CPE status
Puppet Puppet Affected: 5.5.x prior to 5.5.19
Affected: Fixed in 5.5.19
Affected: 6.x prior to 6.13.0
Affected: Fixed in 6.13.0
guessed Create a notification for this product.
Puppet Puppet Agent Affected: 5.5.x prior to 5.5.19
Affected: Fixed in 5.5.19
Affected: 6.x prior to 6.13.0
Affected: Fixed in 6.13.0
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-04T09:48:24.553Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://puppet.com/security/cve/CVE-2020-7942/"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "Puppet",
          "vendor": "Puppet",
          "versions": [
            {
              "status": "affected",
              "version": "5.5.x prior to 5.5.19"
            },
            {
              "status": "affected",
              "version": "Fixed in 5.5.19"
            },
            {
              "status": "affected",
              "version": "6.x prior to 6.13.0"
            },
            {
              "status": "affected",
              "version": "Fixed in 6.13.0"
            }
          ]
        },
        {
          "product": "Puppet Agent",
          "vendor": "Puppet",
          "versions": [
            {
              "status": "affected",
              "version": "5.5.x prior to 5.5.19"
            },
            {
              "status": "affected",
              "version": "Fixed in 5.5.19"
            },
            {
              "status": "affected",
              "version": "6.x prior to 6.13.0"
            },
            {
              "status": "affected",
              "version": "Fixed in 6.13.0"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node\u0027s catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "Arbitrary retrieval",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2020-04-02T19:00:07.000Z",
        "orgId": "ca2a266c-be2f-4d4b-92d0-47b76b1a9c4e",
        "shortName": "puppet"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://puppet.com/security/cve/CVE-2020-7942/"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "security@puppet.com",
          "ID": "CVE-2020-7942",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "Puppet",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "5.5.x prior to 5.5.19"
                          },
                          {
                            "version_value": "Fixed in 5.5.19"
                          },
                          {
                            "version_value": "6.x prior to 6.13.0"
                          },
                          {
                            "version_value": "Fixed in 6.13.0"
                          }
                        ]
                      }
                    },
                    {
                      "product_name": "Puppet Agent",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "5.5.x prior to 5.5.19"
                          },
                          {
                            "version_value": "Fixed in 5.5.19"
                          },
                          {
                            "version_value": "6.x prior to 6.13.0"
                          },
                          {
                            "version_value": "Fixed in 6.13.0"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "Puppet"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node\u0027s catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19"
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "Arbitrary retrieval"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://puppet.com/security/cve/CVE-2020-7942/",
              "refsource": "CONFIRM",
              "url": "https://puppet.com/security/cve/CVE-2020-7942/"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "ca2a266c-be2f-4d4b-92d0-47b76b1a9c4e",
    "assignerShortName": "puppet",
    "cveId": "CVE-2020-7942",
    "datePublished": "2020-02-19T20:52:03.000Z",
    "dateReserved": "2020-01-23T00:00:00.000Z",
    "dateUpdated": "2024-08-04T09:48:24.553Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2020-7942",
      "date": "2026-10-29",
      "epss": "0.00801",
      "percentile": "0.56522"
    },
    "fkie_nvd": {
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:*",
                  "matchCriteriaId": "E1316D93-D540-4E07-97B9-0FD9DAC19D5E",
                  "versionEndExcluding": "5.5.19",
                  "versionStartIncluding": "5.5.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:*",
                  "matchCriteriaId": "2A32C5AF-A28C-464B-949D-570BD98D36C9",
                  "versionEndExcluding": "6.13.0",
                  "versionStartIncluding": "6.0.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:*",
                  "matchCriteriaId": "09EAB60C-0BE2-4FCA-9867-2D6CA4F84F35",
                  "versionEndExcluding": "5.5.19",
                  "versionStartIncluding": "5.5.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:*",
                  "matchCriteriaId": "C76E5E7E-185B-48E7-AC61-C7F97F1B46BC",
                  "versionEndExcluding": "6.13.0",
                  "versionStartIncluding": "6.0.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node\u0027s catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19"
        },
        {
          "lang": "es",
          "value": "Anteriormente, Puppet operaba en un modelo en el que un nodo con un certificado v\u00e1lido ten\u00eda derecho a toda la informaci\u00f3n del sistema y que un certificado comprometido permit\u00eda el acceso a todo en la infraestructura. Cuando el cat\u00e1logo de un nodo retrocede al nodo \"default\", el cat\u00e1logo puede ser recuperado para un nodo diferente mediante la modificaci\u00f3n de datos para una ejecuci\u00f3n de Puppet. Este problema puede ser mitigado al configurar \"strictly_hostname_checking = true\" en \"puppet.conf\" en su maestro de Puppet. Puppet versi\u00f3n 6.13.0 y versi\u00f3n 5.5.19 cambia el comportamiento predeterminado para el strict_hostname_checking de falso a verdadero. Se recomienda que los usuarios de Puppet Open Source y Puppet Enterprise que no est\u00e1n actualizando establezcan stric_nombre_host_checking en verdadero para garantizar un comportamiento seguro. Versiones de software afectadas: Puppet versi\u00f3n 6.x en versiones anteriores a la 6.13.0 Puppet Agent versi\u00f3n 6.x en versiones anteriores a la 6.13.0 Puppet versi\u00f3n 5.5.x en versiones anteriores a la 5.5.19 Puppet Agent versi\u00f3n 5.5.x en versiones anteriores a la 5.5.19 Resuelto en: Puppet versi\u00f3n 6.13.0 Puppet Agente versi\u00f3n 6.13.0 Puppet versi\u00f3n 5.5.19 Puppet Agent versi\u00f3n 5.5.19."
        }
      ],
      "id": "CVE-2020-7942",
      "lastModified": "2024-11-21T05:38:03.537",
      "metrics": {
        "cvssMetricV2": [
          {
            "acInsufInfo": false,
            "baseSeverity": "MEDIUM",
            "cvssData": {
              "accessComplexity": "LOW",
              "accessVector": "NETWORK",
              "authentication": "SINGLE",
              "availabilityImpact": "NONE",
              "baseScore": 4.0,
              "confidentialityImpact": "PARTIAL",
              "integrityImpact": "NONE",
              "vectorString": "AV:N/AC:L/Au:S/C:P/I:N/A:N",
              "version": "2.0"
            },
            "exploitabilityScore": 8.0,
            "impactScore": 2.9,
            "obtainAllPrivilege": false,
            "obtainOtherPrivilege": false,
            "obtainUserPrivilege": false,
            "source": "nvd@nist.gov",
            "type": "Primary",
            "userInteractionRequired": false
          }
        ],
        "cvssMetricV31": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "NONE",
              "baseScore": 6.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "HIGH",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
              "version": "3.1"
            },
            "exploitabilityScore": 2.8,
            "impactScore": 3.6,
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      },
      "published": "2020-02-19T21:15:11.747",
      "references": [
        {
          "source": "security@puppet.com",
          "tags": [
            "Vendor Advisory"
          ],
          "url": "https://puppet.com/security/cve/CVE-2020-7942/"
        },
        {
          "source": "af854a3a-2127-422b-91ae-364da2661108",
          "tags": [
            "Vendor Advisory"
          ],
          "url": "https://puppet.com/security/cve/CVE-2020-7942/"
        }
      ],
      "sourceIdentifier": "security@puppet.com",
      "vulnStatus": "Modified",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-295"
            }
          ],
          "source": "nvd@nist.gov",
          "type": "Primary"
        }
      ]
    },
    "nvd": {
      "cve": {
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "E1316D93-D540-4E07-97B9-0FD9DAC19D5E",
                    "versionEndExcluding": "5.5.19",
                    "versionStartIncluding": "5.5.0",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "2A32C5AF-A28C-464B-949D-570BD98D36C9",
                    "versionEndExcluding": "6.13.0",
                    "versionStartIncluding": "6.0.0",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "09EAB60C-0BE2-4FCA-9867-2D6CA4F84F35",
                    "versionEndExcluding": "5.5.19",
                    "versionStartIncluding": "5.5.0",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "C76E5E7E-185B-48E7-AC61-C7F97F1B46BC",
                    "versionEndExcluding": "6.13.0",
                    "versionStartIncluding": "6.0.0",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node\u0027s catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19"
          },
          {
            "lang": "es",
            "value": "Anteriormente, Puppet operaba en un modelo en el que un nodo con un certificado v\u00e1lido ten\u00eda derecho a toda la informaci\u00f3n del sistema y que un certificado comprometido permit\u00eda el acceso a todo en la infraestructura. Cuando el cat\u00e1logo de un nodo retrocede al nodo \"default\", el cat\u00e1logo puede ser recuperado para un nodo diferente mediante la modificaci\u00f3n de datos para una ejecuci\u00f3n de Puppet. Este problema puede ser mitigado al configurar \"strictly_hostname_checking = true\" en \"puppet.conf\" en su maestro de Puppet. Puppet versi\u00f3n 6.13.0 y versi\u00f3n 5.5.19 cambia el comportamiento predeterminado para el strict_hostname_checking de falso a verdadero. Se recomienda que los usuarios de Puppet Open Source y Puppet Enterprise que no est\u00e1n actualizando establezcan stric_nombre_host_checking en verdadero para garantizar un comportamiento seguro. Versiones de software afectadas: Puppet versi\u00f3n 6.x en versiones anteriores a la 6.13.0 Puppet Agent versi\u00f3n 6.x en versiones anteriores a la 6.13.0 Puppet versi\u00f3n 5.5.x en versiones anteriores a la 5.5.19 Puppet Agent versi\u00f3n 5.5.x en versiones anteriores a la 5.5.19 Resuelto en: Puppet versi\u00f3n 6.13.0 Puppet Agente versi\u00f3n 6.13.0 Puppet versi\u00f3n 5.5.19 Puppet Agent versi\u00f3n 5.5.19."
          }
        ],
        "id": "CVE-2020-7942",
        "lastModified": "2024-11-21T05:38:03.537",
        "metrics": {
          "cvssMetricV2": [
            {
              "acInsufInfo": false,
              "baseSeverity": "MEDIUM",
              "cvssData": {
                "accessComplexity": "LOW",
                "accessVector": "NETWORK",
                "authentication": "SINGLE",
                "availabilityImpact": "NONE",
                "baseScore": 4.0,
                "confidentialityImpact": "PARTIAL",
                "integrityImpact": "NONE",
                "vectorString": "AV:N/AC:L/Au:S/C:P/I:N/A:N",
                "version": "2.0"
              },
              "exploitabilityScore": 8.0,
              "impactScore": 2.9,
              "obtainAllPrivilege": false,
              "obtainOtherPrivilege": false,
              "obtainUserPrivilege": false,
              "source": "nvd@nist.gov",
              "type": "Primary",
              "userInteractionRequired": false
            }
          ],
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "NONE",
                "baseScore": 6.5,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "NONE",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
                "version": "3.1"
              },
              "exploitabilityScore": 2.8,
              "impactScore": 3.6,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ]
        },
        "published": "2020-02-19T21:15:11.747",
        "references": [
          {
            "source": "security@puppet.com",
            "tags": [
              "Vendor Advisory"
            ],
            "url": "https://puppet.com/security/cve/CVE-2020-7942/"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Vendor Advisory"
            ],
            "url": "https://puppet.com/security/cve/CVE-2020-7942/"
          }
        ],
        "sourceIdentifier": "security@puppet.com",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-295"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-03-04T09:31:22+00:00",
      "cve": "CVE-2020-7942",
      "id": "CVE-2020-7942",
      "initial_release_date": "2020-02-18T00:00:00+00:00",
      "product_status:fixed": "1274",
      "product_status:known_affected": "16",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "puppet: Arbitrary catalog retrieval",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2020/cve-2020-7942.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-09-02T02:32:25Z",
      "cve": "CVE-2020-7942",
      "id": "CVE-2020-7942",
      "initial_release_date": "2023-02-15T04:01:44Z",
      "product_status:known_affected": "1",
      "product_status:recommended": "28",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2020-7942",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2020-7942.json",
      "version": "10"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.