CVE-2016-10135 (GCVE-0-2016-10135)

Vulnerability from cvelistv5 – Published: 2017-01-13 09:00 – Updated: 2024-08-06 03:14
VLAI
Summary
An issue was discovered on LG devices using the MTK chipset with L(5.0/5.1), M(6.0/6.0.1), and N(7.0) software, and RCA Voyager Tablet, BLU Advance 5.0, and BLU R1 HD devices. The MTKLogger app with a package name of com.mediatek.mtklogger has application components that are accessible to any application that resides on the device. Namely, the com.mediatek.mtklogger.framework.LogReceiver and com.mediatek.mtklogger.framework.MTKLoggerService application components are exported since they contain an intent filter, are not protected by a custom permission, and do not explicitly set the android:exported attribute to false. Therefore, these components are exported by default and are thus accessible to any third party application by using android.content.Intent object for communication. These application components can be used to start and stop the logs using Intent objects with embedded data. The available logs are the GPS log, modem log, network log, and mobile log. The base directory that contains the directories for the 4 types of logs is /sdcard/mtklog which makes them accessible to apps that require the READ_EXTERNAL_STORAGE permission. The GPS log contains the GPS coordinates of the user as well as a timestamp for the coordinates. The modem log contains AT commands and their parameters which allow the user's outgoing and incoming calls and text messages to be obtained. The network log is a tcpdump network capture. The mobile log contains the Android log, which is not available to third-party apps as of Android 4.1. The LG ID is LVE-SMP-160019.
Severity
5.5 (Medium)
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
CWE
  • n/a
Assigner
mitre CNA under the mitre root
CNA scorecard E 28/100 over 2280 records in the last 180 days details
References
Date Public
2017-01-13 00:00
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-06T03:14:42.039Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://lgsecurity.lge.com/security_updates.html"
          },
          {
            "name": "96846",
            "tags": [
              "vdb-entry",
              "x_refsource_BID",
              "x_transferred"
            ],
            "url": "http://www.securityfocus.com/bid/96846"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "datePublic": "2017-01-13T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "An issue was discovered on LG devices using the MTK chipset with L(5.0/5.1), M(6.0/6.0.1), and N(7.0) software, and RCA Voyager Tablet, BLU Advance 5.0, and BLU R1 HD devices. The MTKLogger app with a package name of com.mediatek.mtklogger has application components that are accessible to any application that resides on the device. Namely, the com.mediatek.mtklogger.framework.LogReceiver and com.mediatek.mtklogger.framework.MTKLoggerService application components are exported since they contain an intent filter, are not protected by a custom permission, and do not explicitly set the android:exported attribute to false. Therefore, these components are exported by default and are thus accessible to any third party application by using android.content.Intent object for communication. These application components can be used to start and stop the logs using Intent objects with embedded data. The available logs are the GPS log, modem log, network log, and mobile log. The base directory that contains the directories for the 4 types of logs is /sdcard/mtklog which makes them accessible to apps that require the READ_EXTERNAL_STORAGE permission. The GPS log contains the GPS coordinates of the user as well as a timestamp for the coordinates. The modem log contains AT commands and their parameters which allow the user\u0027s outgoing and incoming calls and text messages to be obtained. The network log is a tcpdump network capture. The mobile log contains the Android log, which is not available to third-party apps as of Android 4.1. The LG ID is LVE-SMP-160019."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2017-03-15T09:57:01.000Z",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://lgsecurity.lge.com/security_updates.html"
        },
        {
          "name": "96846",
          "tags": [
            "vdb-entry",
            "x_refsource_BID"
          ],
          "url": "http://www.securityfocus.com/bid/96846"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2016-10135",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "An issue was discovered on LG devices using the MTK chipset with L(5.0/5.1), M(6.0/6.0.1), and N(7.0) software, and RCA Voyager Tablet, BLU Advance 5.0, and BLU R1 HD devices. The MTKLogger app with a package name of com.mediatek.mtklogger has application components that are accessible to any application that resides on the device. Namely, the com.mediatek.mtklogger.framework.LogReceiver and com.mediatek.mtklogger.framework.MTKLoggerService application components are exported since they contain an intent filter, are not protected by a custom permission, and do not explicitly set the android:exported attribute to false. Therefore, these components are exported by default and are thus accessible to any third party application by using android.content.Intent object for communication. These application components can be used to start and stop the logs using Intent objects with embedded data. The available logs are the GPS log, modem log, network log, and mobile log. The base directory that contains the directories for the 4 types of logs is /sdcard/mtklog which makes them accessible to apps that require the READ_EXTERNAL_STORAGE permission. The GPS log contains the GPS coordinates of the user as well as a timestamp for the coordinates. The modem log contains AT commands and their parameters which allow the user\u0027s outgoing and incoming calls and text messages to be obtained. The network log is a tcpdump network capture. The mobile log contains the Android log, which is not available to third-party apps as of Android 4.1. The LG ID is LVE-SMP-160019."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://lgsecurity.lge.com/security_updates.html",
              "refsource": "MISC",
              "url": "https://lgsecurity.lge.com/security_updates.html"
            },
            {
              "name": "96846",
              "refsource": "BID",
              "url": "http://www.securityfocus.com/bid/96846"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2016-10135",
    "datePublished": "2017-01-13T09:00:00.000Z",
    "dateReserved": "2017-01-13T00:00:00.000Z",
    "dateUpdated": "2024-08-06T03:14:42.039Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2016-10135",
      "date": "2026-11-03",
      "epss": "0.00928",
      "percentile": "0.6056"
    },
    "fkie_nvd": {
      "configurations": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:lg:lg_mobile:5.0:*:*:*:*:*:*:*",
                  "matchCriteriaId": "CE4185E2-D986-4F05-A3B1-509834A4F2DC",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:lg:lg_mobile:5.1:*:*:*:*:*:*:*",
                  "matchCriteriaId": "C6CFA104-4FA7-4C19-82F4-FBE168D1FF10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:lg:lg_mobile:6.0:*:*:*:*:*:*:*",
                  "matchCriteriaId": "94759827-0B92-496A-96F0-E539AD843976",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:lg:lg_mobile:6.0.1:*:*:*:*:*:*:*",
                  "matchCriteriaId": "4FAB1BDE-011E-4B44-8E23-3031C78E440E",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:lg:lg_mobile:7.0:*:*:*:*:*:*:*",
                  "matchCriteriaId": "F2074A17-35B6-425D-B6AC-954984FEC837",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "An issue was discovered on LG devices using the MTK chipset with L(5.0/5.1), M(6.0/6.0.1), and N(7.0) software, and RCA Voyager Tablet, BLU Advance 5.0, and BLU R1 HD devices. The MTKLogger app with a package name of com.mediatek.mtklogger has application components that are accessible to any application that resides on the device. Namely, the com.mediatek.mtklogger.framework.LogReceiver and com.mediatek.mtklogger.framework.MTKLoggerService application components are exported since they contain an intent filter, are not protected by a custom permission, and do not explicitly set the android:exported attribute to false. Therefore, these components are exported by default and are thus accessible to any third party application by using android.content.Intent object for communication. These application components can be used to start and stop the logs using Intent objects with embedded data. The available logs are the GPS log, modem log, network log, and mobile log. The base directory that contains the directories for the 4 types of logs is /sdcard/mtklog which makes them accessible to apps that require the READ_EXTERNAL_STORAGE permission. The GPS log contains the GPS coordinates of the user as well as a timestamp for the coordinates. The modem log contains AT commands and their parameters which allow the user\u0027s outgoing and incoming calls and text messages to be obtained. The network log is a tcpdump network capture. The mobile log contains the Android log, which is not available to third-party apps as of Android 4.1. The LG ID is LVE-SMP-160019."
        },
        {
          "lang": "es",
          "value": "Se descubri\u00f3 un problema en los dispositivos LG que utilizan el chipset MTK con software L(5.0/5.1), M(6.0/6.0.1) y N(7.0) y dispositivos RCA Voyager Tablet, BLU Advance 5.0 y BLU R1 HD. La aplicaci\u00f3n MTKLogger con un nombre de paquete de com.mediatek.mtklogger tiene componentes de aplicaci\u00f3n que son accesibles para cualquier aplicaci\u00f3n que resida en el dispositivo. Es decir, los componentes de la aplicaci\u00f3n com.mediatek.mtklogger.framework.LogReceiver y com.mediatek.mtklogger.framework.MTKLoggerService se exportan ya que contienen un filtro de intenciones, no est\u00e1n protegidos por un permiso personalizado y no establecen explicitamente Android: exportado a false. Por lo tanto, estos componentes se exportan de forma predeterminada y, por lo tanto, son accesibles a cualquier aplicaci\u00f3n de terceros utilizando el objeto android.content.Intent para la comunicaci\u00f3n. Estos componentes de aplicaci\u00f3n se pueden utilizar para iniciar y detener los registros mediante objetos Intent con datos incrustados. Los registros disponibles son el el registro GPS, el registro del m\u00f3dem, el registro de la red y el registro m\u00f3vil. El directorio base que contiene los directorios para los 4 tipos de registros is /sdcard/mtklog que los hace accesibles a las aplicaciones que requieren el permiso READ_EXTERNAL_STORAGE. El registro GPS del usuario, as\u00ed como una marca de tiempo para las coordenadas. El registro de m\u00f3dem contienen comando AT y sus par\u00e1metro que permiten obtener las llamadas entrantes y salientes del usuario y los mensajes de texto. El registro para tel\u00e9fonos m\u00f3viles contiene el registro de Android, que no est\u00e1 disponible para aplicaciones de terceros desde Android 4.1. El LG ID is LVE-SMP-160019."
        }
      ],
      "id": "CVE-2016-10135",
      "lastModified": "2024-11-21T02:43:22.913",
      "metrics": {
        "cvssMetricV2": [
          {
            "acInsufInfo": false,
            "baseSeverity": "MEDIUM",
            "cvssData": {
              "accessComplexity": "MEDIUM",
              "accessVector": "NETWORK",
              "authentication": "NONE",
              "availabilityImpact": "NONE",
              "baseScore": 4.3,
              "confidentialityImpact": "PARTIAL",
              "integrityImpact": "NONE",
              "vectorString": "AV:N/AC:M/Au:N/C:P/I:N/A:N",
              "version": "2.0"
            },
            "exploitabilityScore": 8.6,
            "impactScore": 2.9,
            "obtainAllPrivilege": false,
            "obtainOtherPrivilege": false,
            "obtainUserPrivilege": false,
            "source": "nvd@nist.gov",
            "type": "Primary",
            "userInteractionRequired": true
          }
        ],
        "cvssMetricV30": [
          {
            "cvssData": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "NONE",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "HIGH",
              "integrityImpact": "NONE",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "REQUIRED",
              "vectorString": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
              "version": "3.0"
            },
            "exploitabilityScore": 1.8,
            "impactScore": 3.6,
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      },
      "published": "2017-01-13T09:59:00.140",
      "references": [
        {
          "source": "cve@mitre.org",
          "url": "http://www.securityfocus.com/bid/96846"
        },
        {
          "source": "cve@mitre.org",
          "tags": [
            "Vendor Advisory"
          ],
          "url": "https://lgsecurity.lge.com/security_updates.html"
        },
        {
          "source": "af854a3a-2127-422b-91ae-364da2661108",
          "url": "http://www.securityfocus.com/bid/96846"
        },
        {
          "source": "af854a3a-2127-422b-91ae-364da2661108",
          "tags": [
            "Vendor Advisory"
          ],
          "url": "https://lgsecurity.lge.com/security_updates.html"
        }
      ],
      "sourceIdentifier": "cve@mitre.org",
      "vulnStatus": "Modified",
      "weaknesses": [
        {
          "description": [
            {
              "lang": "en",
              "value": "CWE-200"
            }
          ],
          "source": "nvd@nist.gov",
          "type": "Primary"
        }
      ]
    },
    "nvd": {
      "cve": {
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:o:lg:lg_mobile:5.0:*:*:*:*:*:*:*",
                    "matchCriteriaId": "CE4185E2-D986-4F05-A3B1-509834A4F2DC",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:lg:lg_mobile:5.1:*:*:*:*:*:*:*",
                    "matchCriteriaId": "C6CFA104-4FA7-4C19-82F4-FBE168D1FF10",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:lg:lg_mobile:6.0:*:*:*:*:*:*:*",
                    "matchCriteriaId": "94759827-0B92-496A-96F0-E539AD843976",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:lg:lg_mobile:6.0.1:*:*:*:*:*:*:*",
                    "matchCriteriaId": "4FAB1BDE-011E-4B44-8E23-3031C78E440E",
                    "vulnerable": true
                  },
                  {
                    "criteria": "cpe:2.3:o:lg:lg_mobile:7.0:*:*:*:*:*:*:*",
                    "matchCriteriaId": "F2074A17-35B6-425D-B6AC-954984FEC837",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "An issue was discovered on LG devices using the MTK chipset with L(5.0/5.1), M(6.0/6.0.1), and N(7.0) software, and RCA Voyager Tablet, BLU Advance 5.0, and BLU R1 HD devices. The MTKLogger app with a package name of com.mediatek.mtklogger has application components that are accessible to any application that resides on the device. Namely, the com.mediatek.mtklogger.framework.LogReceiver and com.mediatek.mtklogger.framework.MTKLoggerService application components are exported since they contain an intent filter, are not protected by a custom permission, and do not explicitly set the android:exported attribute to false. Therefore, these components are exported by default and are thus accessible to any third party application by using android.content.Intent object for communication. These application components can be used to start and stop the logs using Intent objects with embedded data. The available logs are the GPS log, modem log, network log, and mobile log. The base directory that contains the directories for the 4 types of logs is /sdcard/mtklog which makes them accessible to apps that require the READ_EXTERNAL_STORAGE permission. The GPS log contains the GPS coordinates of the user as well as a timestamp for the coordinates. The modem log contains AT commands and their parameters which allow the user\u0027s outgoing and incoming calls and text messages to be obtained. The network log is a tcpdump network capture. The mobile log contains the Android log, which is not available to third-party apps as of Android 4.1. The LG ID is LVE-SMP-160019."
          },
          {
            "lang": "es",
            "value": "Se descubri\u00f3 un problema en los dispositivos LG que utilizan el chipset MTK con software L(5.0/5.1), M(6.0/6.0.1) y N(7.0) y dispositivos RCA Voyager Tablet, BLU Advance 5.0 y BLU R1 HD. La aplicaci\u00f3n MTKLogger con un nombre de paquete de com.mediatek.mtklogger tiene componentes de aplicaci\u00f3n que son accesibles para cualquier aplicaci\u00f3n que resida en el dispositivo. Es decir, los componentes de la aplicaci\u00f3n com.mediatek.mtklogger.framework.LogReceiver y com.mediatek.mtklogger.framework.MTKLoggerService se exportan ya que contienen un filtro de intenciones, no est\u00e1n protegidos por un permiso personalizado y no establecen explicitamente Android: exportado a false. Por lo tanto, estos componentes se exportan de forma predeterminada y, por lo tanto, son accesibles a cualquier aplicaci\u00f3n de terceros utilizando el objeto android.content.Intent para la comunicaci\u00f3n. Estos componentes de aplicaci\u00f3n se pueden utilizar para iniciar y detener los registros mediante objetos Intent con datos incrustados. Los registros disponibles son el el registro GPS, el registro del m\u00f3dem, el registro de la red y el registro m\u00f3vil. El directorio base que contiene los directorios para los 4 tipos de registros is /sdcard/mtklog que los hace accesibles a las aplicaciones que requieren el permiso READ_EXTERNAL_STORAGE. El registro GPS del usuario, as\u00ed como una marca de tiempo para las coordenadas. El registro de m\u00f3dem contienen comando AT y sus par\u00e1metro que permiten obtener las llamadas entrantes y salientes del usuario y los mensajes de texto. El registro para tel\u00e9fonos m\u00f3viles contiene el registro de Android, que no est\u00e1 disponible para aplicaciones de terceros desde Android 4.1. El LG ID is LVE-SMP-160019."
          }
        ],
        "id": "CVE-2016-10135",
        "lastModified": "2026-05-13T00:24:29.033",
        "metrics": {
          "cvssMetricV2": [
            {
              "acInsufInfo": false,
              "baseSeverity": "MEDIUM",
              "cvssData": {
                "accessComplexity": "MEDIUM",
                "accessVector": "NETWORK",
                "authentication": "NONE",
                "availabilityImpact": "NONE",
                "baseScore": 4.3,
                "confidentialityImpact": "PARTIAL",
                "integrityImpact": "NONE",
                "vectorString": "AV:N/AC:M/Au:N/C:P/I:N/A:N",
                "version": "2.0"
              },
              "exploitabilityScore": 8.6,
              "impactScore": 2.9,
              "obtainAllPrivilege": false,
              "obtainOtherPrivilege": false,
              "obtainUserPrivilege": false,
              "source": "nvd@nist.gov",
              "type": "Primary",
              "userInteractionRequired": true
            }
          ],
          "cvssMetricV30": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "LOCAL",
                "availabilityImpact": "NONE",
                "baseScore": 5.5,
                "baseSeverity": "MEDIUM",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "NONE",
                "privilegesRequired": "NONE",
                "scope": "UNCHANGED",
                "userInteraction": "REQUIRED",
                "vectorString": "CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
                "version": "3.0"
              },
              "exploitabilityScore": 1.8,
              "impactScore": 3.6,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ]
        },
        "published": "2017-01-13T09:59:00.140",
        "references": [
          {
            "source": "cve@mitre.org",
            "url": "http://www.securityfocus.com/bid/96846"
          },
          {
            "source": "cve@mitre.org",
            "tags": [
              "Vendor Advisory"
            ],
            "url": "https://lgsecurity.lge.com/security_updates.html"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "url": "http://www.securityfocus.com/bid/96846"
          },
          {
            "source": "af854a3a-2127-422b-91ae-364da2661108",
            "tags": [
              "Vendor Advisory"
            ],
            "url": "https://lgsecurity.lge.com/security_updates.html"
          }
        ],
        "sourceIdentifier": "cve@mitre.org",
        "vulnStatus": "Modified",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-200"
              }
            ],
            "source": "nvd@nist.gov",
            "type": "Primary"
          }
        ]
      }
    }
  }
}



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.