CVE-2024-43806 (GCVE-0-2024-43806)

Vulnerability from cvelistv5 – Published: 2024-08-26 18:43 – Updated: 2024-08-26 19:40
VLAI
Title
`rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion
Summary
Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `rustix::fs::Dir` using the `linux_raw` backend, it's possible for the iterator to "get stuck" when an IO error is encountered. Combined with a memory over-allocation issue in `rustix::fs::Dir::read_more`, this can cause quick and unbounded memory explosion (gigabytes in a few seconds if used on a hot path) and eventually lead to an OOM crash of the application. The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. Full details can be read on the GHSA-c827-hfw6-qwvm repo advisory. If a program tries to access a directory with its file descriptor after the file has been unlinked (or any other action that leaves the `Dir` iterator in the stuck state), and the implementation does not break after seeing an error, it can cause a memory explosion. As an example, Linux's various virtual file systems (e.g. `/proc`, `/sys`) can contain directories that spontaneously pop in and out of existence. Attempting to iterate over them using `rustix::fs::Dir` directly or indirectly (e.g. with the `procfs` crate) can trigger this fault condition if the implementation decides to continue on errors. An attacker knowledgeable about the implementation details of a vulnerable target can therefore try to trigger this fault condition via any one or a combination of several available APIs. If successful, the application host will quickly run out of memory, after which the application will likely be terminated by an OOM killer, leading to denial of service. This issue has been addressed in release versions 0.35.15, 0.36.16, 0.37.25, and 0.38.19. Users are advised to upgrade. There are no known workarounds for this issue.
Severity
6.5 (Medium)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
SSVC
Exploitation: poc Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2024-08-26 19:37 UTC
CWE
  • CWE-400 - Uncontrolled Resource Consumption
Assigner
GitHub_M CNA under the mitre root
CNA scorecard C 72/100 over 7868 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
bytecodealliance rustix Affected: >= 0.35.11, < 0.35.15
Affected: >= 0.36.0, < 0.36.16
Affected: >= 0.37.0, < 0.37.25
Affected: >= 0.38.0, < 0.38.19
guessed Create a notification for this product.
bytecodealliance rustix Affected: 0.35.11 , < 0.35.15 (custom)
Affected: 0.36.0 , < 0.36.16 (custom)
Affected: 0.37.0 , < 0.37.25 (custom)
Affected: 0.38.0 , < 0.38.19 (custom)
    cpe:2.3:a:bytecodealliance:rustix:*:*:*:*:*:*:*:*
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "affected": [
          {
            "cpes": [
              "cpe:2.3:a:bytecodealliance:rustix:*:*:*:*:*:*:*:*"
            ],
            "defaultStatus": "unknown",
            "product": "rustix",
            "vendor": "bytecodealliance",
            "versions": [
              {
                "lessThan": "0.35.15",
                "status": "affected",
                "version": "0.35.11",
                "versionType": "custom"
              },
              {
                "lessThan": "0.36.16",
                "status": "affected",
                "version": "0.36.0",
                "versionType": "custom"
              },
              {
                "lessThan": "0.37.25",
                "status": "affected",
                "version": "0.37.0",
                "versionType": "custom"
              },
              {
                "lessThan": "0.38.19",
                "status": "affected",
                "version": "0.38.0",
                "versionType": "custom"
              }
            ]
          }
        ],
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-43806",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-08-26T19:37:59.015162Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-08-26T19:40:46.911Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "rustix",
          "vendor": "bytecodealliance",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 0.35.11, \u003c 0.35.15"
            },
            {
              "status": "affected",
              "version": "\u003e= 0.36.0, \u003c 0.36.16"
            },
            {
              "status": "affected",
              "version": "\u003e= 0.37.0, \u003c 0.37.25"
            },
            {
              "status": "affected",
              "version": "\u003e= 0.38.0, \u003c 0.38.19"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `rustix::fs::Dir` using the `linux_raw` backend, it\u0027s possible for the iterator to \"get stuck\" when an IO error is encountered. Combined with a memory over-allocation issue in `rustix::fs::Dir::read_more`, this can cause quick and unbounded memory explosion (gigabytes in a few seconds if used on a hot path) and eventually lead to an OOM crash of the application. The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. Full details can be read on the GHSA-c827-hfw6-qwvm repo advisory. If a program tries to access a directory with its file descriptor after the file has been unlinked (or any other action that leaves the `Dir` iterator in the stuck state), and the implementation does not break after seeing an error, it can cause a memory explosion. As an example, Linux\u0027s various virtual file systems (e.g. `/proc`, `/sys`) can contain directories that spontaneously pop in and out of existence. Attempting to iterate over them using `rustix::fs::Dir` directly or indirectly (e.g. with the `procfs` crate) can trigger this fault condition if the implementation decides to continue on errors. An attacker knowledgeable about the implementation details of a vulnerable target can therefore try to trigger this fault condition via any one or a combination of several available APIs. If successful, the application host will quickly run out of memory, after which the application will likely be terminated by an OOM killer, leading to denial of service. This issue has been addressed in release versions 0.35.15, 0.36.16, 0.37.25, and 0.38.19. Users are advised to upgrade. There are no known workarounds for this issue."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "HIGH",
            "baseScore": 6.5,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "NONE",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-400",
              "description": "CWE-400: Uncontrolled Resource Consumption",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-08-26T18:43:22.626Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm"
        },
        {
          "name": "https://github.com/imsnif/bandwhich/issues/284",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/imsnif/bandwhich/issues/284"
        }
      ],
      "source": {
        "advisory": "GHSA-c827-hfw6-qwvm",
        "discovery": "UNKNOWN"
      },
      "title": "`rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2024-43806",
    "datePublished": "2024-08-26T18:43:22.626Z",
    "dateReserved": "2024-08-16T14:20:37.326Z",
    "dateUpdated": "2024-08-26T19:40:46.911Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-43806",
      "date": "2026-11-14",
      "epss": "0.0048",
      "percentile": "0.4201"
    },
    "microsoft_vex": {
      "current_release_date": "2026-02-18T15:16:51.000Z",
      "cve": "CVE-2024-43806",
      "id": "msrc_CVE-2024-43806",
      "initial_release_date": "2024-08-02T00:00:00.000Z",
      "product_status:fixed": "13",
      "product_status:known_affected": "13",
      "product_status:known_not_affected": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "`rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion",
      "url": "https://msrc.microsoft.com/csaf/vex/2024/msrc_cve-2024-43806.json",
      "version": "8"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "product": "rustix",
                "vendor": "bytecodealliance",
                "versions": [
                  {
                    "status": "affected",
                    "version": "\u003e= 0.35.11, \u003c 0.35.15"
                  },
                  {
                    "status": "affected",
                    "version": "\u003e= 0.36.0, \u003c 0.36.16"
                  },
                  {
                    "status": "affected",
                    "version": "\u003e= 0.37.0, \u003c 0.37.25"
                  },
                  {
                    "status": "affected",
                    "version": "\u003e= 0.38.0, \u003c 0.38.19"
                  }
                ]
              }
            ],
            "source": "security-advisories@github.com"
          },
          {
            "affectedData": [
              {
                "cpes": [
                  "cpe:2.3:a:bytecodealliance:rustix:*:*:*:*:*:*:*:*"
                ],
                "defaultStatus": "unknown",
                "product": "rustix",
                "vendor": "bytecodealliance",
                "versions": [
                  {
                    "lessThan": "0.35.15",
                    "status": "affected",
                    "version": "0.35.11",
                    "versionType": "custom"
                  },
                  {
                    "lessThan": "0.36.16",
                    "status": "affected",
                    "version": "0.36.0",
                    "versionType": "custom"
                  },
                  {
                    "lessThan": "0.37.25",
                    "status": "affected",
                    "version": "0.37.0",
                    "versionType": "custom"
                  },
                  {
                    "lessThan": "0.38.19",
                    "status": "affected",
                    "version": "0.38.0",
                    "versionType": "custom"
                  }
                ]
              }
            ],
            "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `rustix::fs::Dir` using the `linux_raw` backend, it\u0027s possible for the iterator to \"get stuck\" when an IO error is encountered. Combined with a memory over-allocation issue in `rustix::fs::Dir::read_more`, this can cause quick and unbounded memory explosion (gigabytes in a few seconds if used on a hot path) and eventually lead to an OOM crash of the application. The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. Full details can be read on the GHSA-c827-hfw6-qwvm repo advisory. If a program tries to access a directory with its file descriptor after the file has been unlinked (or any other action that leaves the `Dir` iterator in the stuck state), and the implementation does not break after seeing an error, it can cause a memory explosion. As an example, Linux\u0027s various virtual file systems (e.g. `/proc`, `/sys`) can contain directories that spontaneously pop in and out of existence. Attempting to iterate over them using `rustix::fs::Dir` directly or indirectly (e.g. with the `procfs` crate) can trigger this fault condition if the implementation decides to continue on errors. An attacker knowledgeable about the implementation details of a vulnerable target can therefore try to trigger this fault condition via any one or a combination of several available APIs. If successful, the application host will quickly run out of memory, after which the application will likely be terminated by an OOM killer, leading to denial of service. This issue has been addressed in release versions 0.35.15, 0.36.16, 0.37.25, and 0.38.19. Users are advised to upgrade. There are no known workarounds for this issue."
          },
          {
            "lang": "es",
            "value": "Rustix es un conjunto de enlaces seguros de Rust para API tipo POSIX. Cuando se usa `rustix::fs::Dir` usando el backend `linux_raw`, es posible que el iterador se \"quede atascado\" cuando se encuentra un error de IO. Combinado con un problema de sobreasignaci\u00f3n de memoria en `rustix::fs::Dir::read_more`, esto puede causar una explosi\u00f3n de memoria r\u00e1pida e ilimitada (gigabytes en unos pocos segundos si se usa en una ruta activa) y eventualmente provocar un bloqueo de OOM. de la aplicaci\u00f3n. Los s\u00edntomas se descubrieron inicialmente en https://github.com/imsnif/band Which/issues/284. Esa publicaci\u00f3n tiene muchos detalles de nuestra investigaci\u00f3n. Se pueden leer todos los detalles en el aviso de repositorio GHSA-c827-hfw6-qwvm. Si un programa intenta acceder a un directorio con su descriptor de archivo despu\u00e9s de que el archivo se ha desvinculado (o cualquier otra acci\u00f3n que deje el iterador `Dir` en estado bloqueado), y la implementaci\u00f3n no se interrumpe despu\u00e9s de ver un error, puede causar una explosi\u00f3n de memoria. Como ejemplo, los diversos sistemas de archivos virtuales de Linux (por ejemplo, `/proc`, `/sys`) pueden contener directorios que aparecen y desaparecen espont\u00e1neamente. Intentar iterar sobre ellos usando `rustix::fs::Dir` directa o indirectamente (por ejemplo, con la caja `procfs`) puede desencadenar esta condici\u00f3n de falla si la implementaci\u00f3n decide continuar con los errores. Por lo tanto, un atacante que conozca los detalles de implementaci\u00f3n de un objetivo vulnerable puede intentar desencadenar esta condici\u00f3n de error a trav\u00e9s de cualquiera o una combinaci\u00f3n de varias API disponibles. Si tiene \u00e9xito, el host de la aplicaci\u00f3n se quedar\u00e1 r\u00e1pidamente sin memoria, despu\u00e9s de lo cual es probable que un asesino OOM finalice la aplicaci\u00f3n, lo que provocar\u00e1 una denegaci\u00f3n de servicio. Este problema se solucion\u00f3 en las versiones 0.35.15, 0.36.16, 0.37.25 y 0.38.19. Se recomienda a los usuarios que actualicen. No se conocen workarounds para este problema."
          }
        ],
        "id": "CVE-2024-43806",
        "lastModified": "2026-06-17T07:51:44.960",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 6.5,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 2.8,
              "impactScore": 3.6,
              "source": "security-advisories@github.com",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2024-43806",
                "options": [
                  {
                    "exploitation": "poc"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-08-26T19:37:59.015162Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2024-08-26T19:15:08.190",
        "references": [
          {
            "source": "security-advisories@github.com",
            "url": "https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm"
          },
          {
            "source": "security-advisories@github.com",
            "url": "https://github.com/imsnif/bandwhich/issues/284"
          }
        ],
        "sourceIdentifier": "security-advisories@github.com",
        "vulnStatus": "Deferred",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-400"
              }
            ],
            "source": "security-advisories@github.com",
            "type": "Secondary"
          }
        ]
      }
    },
    "redhat_vex": {
      "current_release_date": "2025-05-28T21:24:03+00:00",
      "cve": "CVE-2024-43806",
      "id": "CVE-2024-43806",
      "initial_release_date": "2024-01-01T00:00:00+00:00",
      "product_status:known_not_affected": "1",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "`rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-43806.json",
      "version": "3"
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "affected": [
              {
                "cpes": [
                  "cpe:2.3:a:bytecodealliance:rustix:*:*:*:*:*:*:*:*"
                ],
                "defaultStatus": "unknown",
                "product": "rustix",
                "vendor": "bytecodealliance",
                "versions": [
                  {
                    "lessThan": "0.35.15",
                    "status": "affected",
                    "version": "0.35.11",
                    "versionType": "custom"
                  },
                  {
                    "lessThan": "0.36.16",
                    "status": "affected",
                    "version": "0.36.0",
                    "versionType": "custom"
                  },
                  {
                    "lessThan": "0.37.25",
                    "status": "affected",
                    "version": "0.37.0",
                    "versionType": "custom"
                  },
                  {
                    "lessThan": "0.38.19",
                    "status": "affected",
                    "version": "0.38.0",
                    "versionType": "custom"
                  }
                ]
              }
            ],
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2024-43806",
                    "options": [
                      {
                        "Exploitation": "poc"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2024-08-26T19:37:59.015162Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2024-08-26T19:40:36.419Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "product": "rustix",
              "vendor": "bytecodealliance",
              "versions": [
                {
                  "status": "affected",
                  "version": "\u003e= 0.35.11, \u003c 0.35.15"
                },
                {
                  "status": "affected",
                  "version": "\u003e= 0.36.0, \u003c 0.36.16"
                },
                {
                  "status": "affected",
                  "version": "\u003e= 0.37.0, \u003c 0.37.25"
                },
                {
                  "status": "affected",
                  "version": "\u003e= 0.38.0, \u003c 0.38.19"
                }
              ]
            }
          ],
          "descriptions": [
            {
              "lang": "en",
              "value": "Rustix is a set of safe Rust bindings to POSIX-ish APIs. When using `rustix::fs::Dir` using the `linux_raw` backend, it\u0027s possible for the iterator to \"get stuck\" when an IO error is encountered. Combined with a memory over-allocation issue in `rustix::fs::Dir::read_more`, this can cause quick and unbounded memory explosion (gigabytes in a few seconds if used on a hot path) and eventually lead to an OOM crash of the application. The symptoms were initially discovered in https://github.com/imsnif/bandwhich/issues/284. That post has lots of details of our investigation. Full details can be read on the GHSA-c827-hfw6-qwvm repo advisory. If a program tries to access a directory with its file descriptor after the file has been unlinked (or any other action that leaves the `Dir` iterator in the stuck state), and the implementation does not break after seeing an error, it can cause a memory explosion. As an example, Linux\u0027s various virtual file systems (e.g. `/proc`, `/sys`) can contain directories that spontaneously pop in and out of existence. Attempting to iterate over them using `rustix::fs::Dir` directly or indirectly (e.g. with the `procfs` crate) can trigger this fault condition if the implementation decides to continue on errors. An attacker knowledgeable about the implementation details of a vulnerable target can therefore try to trigger this fault condition via any one or a combination of several available APIs. If successful, the application host will quickly run out of memory, after which the application will likely be terminated by an OOM killer, leading to denial of service. This issue has been addressed in release versions 0.35.15, 0.36.16, 0.37.25, and 0.38.19. Users are advised to upgrade. There are no known workarounds for this issue."
            }
          ],
          "metrics": [
            {
              "cvssV3_1": {
                "attackComplexity": "LOW",
                "attackVector": "NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 6.5,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "NONE",
                "integrityImpact": "NONE",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
                "version": "3.1"
              }
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-400",
                  "description": "CWE-400: Uncontrolled Resource Consumption",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2024-08-26T18:43:22.626Z",
            "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
            "shortName": "GitHub_M"
          },
          "references": [
            {
              "name": "https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm",
              "tags": [
                "x_refsource_CONFIRM"
              ],
              "url": "https://github.com/bytecodealliance/rustix/security/advisories/GHSA-c827-hfw6-qwvm"
            },
            {
              "name": "https://github.com/imsnif/bandwhich/issues/284",
              "tags": [
                "x_refsource_MISC"
              ],
              "url": "https://github.com/imsnif/bandwhich/issues/284"
            }
          ],
          "source": {
            "advisory": "GHSA-c827-hfw6-qwvm",
            "discovery": "UNKNOWN"
          },
          "title": "`rustix::fs::Dir` iterator with the `linux_raw` backend can cause memory explosion"
        }
      },
      "cveMetadata": {
        "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "assignerShortName": "GitHub_M",
        "cveId": "CVE-2024-43806",
        "datePublished": "2024-08-26T18:43:22.626Z",
        "dateReserved": "2024-08-16T14:20:37.326Z",
        "dateUpdated": "2024-08-26T19:40:46.911Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}



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.