GCVE-1988-2026-0341

Vulnerability from gna-1988 – Published: 2026-09-11 07:55 – Updated: 2026-09-11 07:55
VLAI
Title
SEC Consult SA-20260615-1 :: Multiple Vulnerabilities in Wertheim SafeController Hardware for VAULT ROOMS (Safe Deposit Locker System – Microcontroller)
Summary
SEC Consult Vulnerability Lab Security Advisory < 20260615-1 > ======================================================================= title: Multiple Vulnerabilities           product: Wertheim SafeController Hardware for VAULT ROOMS (Safe Deposit Locker System – Microcontroller) vulnerable version: Controller 65000 - AssemblyVersion 6.11.8130.22319                     Controller 5400 - AssemblyVersion 6.11.8130.22320       fixed version: No fix for issue 1 & 2, No information provided for issue 3 CVE number: CVE-2026-34021, CVE-2026-34022              impact: High homepage:https://wertheim-safes.com/safe-deposit-boxes/               found: 2023-04-03 by: Gorazd Jank (Office Vienna) Christian Hager (Office Vienna) Philipp Espernberger (Office Vienna)                      SEC Consult Vulnerability Lab An integrated part of SEC Consult, an Atos business Europe | Asia https://www.sec-consult.com ======================================================================= Vendor description: ------------------- "On September 1, 1852, Franz Wertheim and 85 employees began to build "fireproof safes". Then as now, Wertheim has been successfully involved in production of safes and banking facilities, nationally and internationally. To secure the market position and develop new business areas, Wertheim has continuously adapted its product range over the years as well as expanded its assortment of offerings. Today, the Wertheim Group of companies also produces bank and object furnishings in our own joinery in Uttendorf, and Commissioned Work has developed into an essential business area for the group. The diversity of state-of-the-art technologies characterizes the flexibility and technical know-how of this division." Source:https://wertheim.at/en/company/ (2023) Business recommendation: ------------------------ The affected HW controller 5400 is marked as end-of-life (EOL), hence there won't be any patches provided by the vendor. The encryption algorithm for Controller 65000 cannot be improved/fixed by the vendor as well because of missing hardware support. It is recommended to assess the business risk and switch to a supported version in case any EOL products are used. Vulnerability overview/description: ----------------------------------- 1) Lack of Cryptographic Protection on SafeController 5400 (CVE-2026-34021) The serial communication between the micro controller and the server is not cryptographically protected. An attacker who has already compromised the server or is able to capture the traffic between the server and the micro controller is able to sniff all RS-485 messages and use the sniffed message for replay attacks. This weakness can be used to spoof the message "quit alarm" to continuously deactivate the safe alarm. 2) Insufficient Transport Layer Encryption on SafeController 65000 (CVE-2026-34022) The SafeController Family 65000 is secured with weak and custom cryptographic algorithms with hard-coded keys. An attacker who is in an adversary-in-the-middle position can read and decrypt the data traffic. 3) Undisclosed Vulnerability in the binary SafeController This vulnerability was identified during a reassessment commissioned by Wertheim. Detailed disclosure is withheld as the finding is subject to the vendor's ownership and disclosure authority. Affected parties are advised to contact the vendor directly for further information. Proof of concept: ----------------- 1) Lack of Cryptographic Protection on SafeController 5400 (CVE-2026-34021) ``` Proof of concept removed because no patch will be provided ``` 2) Insufficient Transport Layer Encryption on SafeController 65000 (CVE-2026-34022) ``` Proof of concept removed because no patch will be provided ``` 3) Undisclosed Vulnerability in the binary SafeController ``` Proof of concept removed because of undisclosed vulnerability ``` Vulnerable / tested versions: ----------------------------- The following versions/devices have been tested which were the latest version available at the time of the test: * Wertheim GmbH Safe Service for controller 65000 in AssemblyVersion 6.11.8130.22319 * Wertheim GmbH Safe Service for controller 5400 in AssemblyVersion 6.11.8130.22320 Vendor contact timeline: ------------------------ 2023-06-20: Initial meeting between SEC Consult and Wertheim to discuss identified vulnerabilities 2023-07-23: Contacting vendor through direct email addresses received in the meetings, asking for encryption keys. 2023-07-31: Vendor response to send advisory unencrypted and apologizing for delays due to vacation time. 2023-08-07: Sending two advisories (split between HW devices and SW issues) to vendor, zipped with password. 2023-08-07: Vendor response: project start in September, implementation process planned to be finished early December. Estimation that rollout of patches takes another quarter (end of Q1/24). 2023-08-08: Meeting to discuss further steps. 2023-10-13: Asking for status update via email; No response received. 2023-11-30: Asking for status update via email - as no answer has yet been received. 2023-11-30: Vendor responds to our request with following information: - Currently on time - Release plan Q1/2024 - A meeting between SEC Consult and Wertheim should take place in Q1 to discuss further steps, including the recheck of vulnerabilities. - Updates are provided in different ways: 1. Customers with a support package receive the releases immediately 2. Customers without a support package receive an offer to upgrade. 2024-02-16: Asking for status update and proposed dates for the planned meeting in Q1/2024 via email 2024-02-16: Vendor responds with following information: - A recheck was arranged with SEC Consult to check the mitigations - Recheck date planned for March 2024. 2024-02-22: Vendor has submitted an internal project plan with information and the status of ongoing remedial measures. 2024-02-26: Meeting with the vendor to discuss next steps and recheck date: - After the new review, the remaining weaknesses will be fixed and everything will be rolled out to customers by September 2024 at the latest. 2024-03-05: Recheck date finalized for end of March. 2024-03-29: Recheck conducted with the following results: - Vulnerability 1: Not Fixed - No patch will be provided because the controller is marked as End-of-Life (EOL) - Vulnerability 2: Not Fixed - The algorithm was not changed. Furthermore, it was possible to break the encryption and decryption routine. It is possible to decrypt messages without any knowledge of the encryption key. Furthermore, it is also possible to gain knowledge about the encryption key by intercepting enough messages. - Vulnerability 3: New - Undisclosed Vulnerability in the binary SafeController 2024-06-17: Asking for status update via email; No response received. 2024-09-25: Asking for status update via email. 2024-10-10: The vendor responds to our request and informs us about the following remediation status: - Vulnerability 1: Cannot be fixed due to missing hardware support. - Vulnerability 2: Cannot be fixed due to missing hardware support. - Vulnerability 3: Fixed 2024-10-18: Asking about the publication of new vulnerabilities identified during the recheck, the version number in which the vulnerabilities were fixed, and a workaround for unfixed vulnerabilities. 2024-10-30: Coordination meeting regarding the questions raised. 2024-12-16: Asking for a status update regarding version numbers. Sending updated advisory with PoCs partially redacted. No response. 2025-02-19: Asking for an update; no response 2025-03-18: Asking for an update; no response 2026-03-25: Sending final advisory to Wertheim for approval including a publication date. No response. 2026-04-23: Asking for a status update. No response. 2026-06-11: Informing vendor about upcoming release. 2026-06-15: Release of security advisory. Solution: --------- The affected HW controller 5400 is marked as end-of-life (EOL), hence there won't be any patches provided by the vendor. The encryption algorithm for Controller 65000 cannot be improved/fixed by the vendor as well because of missing hardware support. It is recommended to assess the business risk and switch to a supported version in case any EOL products are used. Workaround: ----------- As an interim mitigation, the following measures are strongly recommended: — Physically isolate all SafeController devices to ensure that only authorized personnel can access them. — Harden all connected devices that communicate via the serial interface, including the application of restrictive configurations and disabling of unnecessary services. — Ensure that servers communicating with the SafeController devices via the serial interface are secured with strong, unique authentication credentials. The use of default, shared, or weak credentials must be avoided. Access should be restricted exclusively to authorized personnel with a legitimate operational need. — Ensure physical security of all interconnected components to prevent unauthorized physical access or tampering. These measures should remain in place until the vendor provides a verified and comprehensive remediation. Advisory URL: ------------- https://sec-consult.com/vulnerability-lab/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SEC Consult Vulnerability Lab An integrated part of SEC Consult, an Atos business Europe | Asia About SEC Consult Vulnerability Lab The SEC Consult Vulnerability Lab is an integrated part of SEC Consult, an Atos business. It ensures the continued knowledge gain of SEC Consult in the field of network and application security to stay ahead of the attacker. The SEC Consult Vulnerability Lab supports high-quality penetration testing and the evaluation of new offensive and defensive technologies for our customers. Hence our customers obtain the most current information about vulnerabilities and valid recommendation about the risk profile of new technologies. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Interested to work with the experts of SEC Consult? Send us your applicationhttps://sec-consult.com/career/ Interested in improving your cyber security with the experts of SEC Consult? Contact our local officeshttps://sec-consult.com/contact/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Mail: security-research at sec-consult dot com Web:https://www.sec-consult.com Blog:http://blog.sec-consult.com X:https://x.com/sec_consult EOF Gorazd Jank, Christian Hager, Philipp Espernberger / @2026 _______________________________________________ Sent through the Full Disclosure mailing list https://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: https://seclists.org/fulldisclosure/
Severity
No CVSS data available.
Assigner
References
Impacted products
Credits
SEC Consult Vulnerability Lab via Fulldisclosure
Relationships
analysis GCVE-1988-2026-0341 (this record)
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "product": "Wertheim SafeController Hardware for VAULT ROOMS",
          "vendor": "unknown",
          "versions": [
            {
              "status": "affected",
              "version": "unknown"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "SEC Consult Vulnerability Lab via Fulldisclosure"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "SEC Consult Vulnerability Lab Security Advisory \u003c 20260615-1 \u003e\n=======================================================================\n              title: Multiple Vulnerabilities\n  \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 product: Wertheim SafeController Hardware for VAULT ROOMS\n                     (Safe Deposit Locker System \u2013 Microcontroller)\n vulnerable version: Controller 65000 - AssemblyVersion 6.11.8130.22319\n \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 Controller 5400 - AssemblyVersion 6.11.8130.22320\n\u00a0 \u00a0 \u00a0 fixed version: No fix for issue 1 \u0026 2,\n                     No information provided for issue 3\n         CVE number: CVE-2026-34021, CVE-2026-34022\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0impact: High\n           homepage:https://wertheim-safes.com/safe-deposit-boxes/\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 found: 2023-04-03\n                 by: Gorazd Jank (Office Vienna)\n                     Christian Hager (Office Vienna)\n                     Philipp Espernberger (Office Vienna)\n\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0SEC Consult Vulnerability Lab\n\n                     An integrated part of SEC Consult, an Atos business\n                     Europe | Asia\n\n                     https://www.sec-consult.com\n\n=======================================================================\n\nVendor description:\n-------------------\n\"On September 1, 1852, Franz Wertheim and 85 employees began to build \"fireproof safes\".\nThen as now, Wertheim has been successfully involved in production of safes and banking\nfacilities, nationally and internationally. To secure the market position and develop\nnew business areas, Wertheim has continuously adapted its product range over the years\nas well as expanded its assortment of offerings. Today, the Wertheim Group of companies\nalso produces bank and object furnishings in our own joinery in Uttendorf, and\nCommissioned Work has developed into an essential business area for the group. The\ndiversity of state-of-the-art technologies characterizes the flexibility and technical\nknow-how of this division.\"\n\nSource:https://wertheim.at/en/company/ (2023)\n\n\nBusiness recommendation:\n------------------------\nThe affected HW controller 5400 is marked as end-of-life (EOL), hence there won\u0027t\nbe any patches provided by the vendor. The encryption algorithm for Controller 65000\ncannot be improved/fixed by the vendor as well because of missing hardware support.\n\nIt is recommended to assess the business risk and switch to a supported version in case\nany EOL products are used.\n\n\nVulnerability overview/description:\n-----------------------------------\n1) Lack of Cryptographic Protection on SafeController 5400 (CVE-2026-34021)\nThe serial communication between the micro controller and the server is not\ncryptographically protected. An attacker who has already compromised the server or\nis able to capture the traffic between the server and the micro controller is able\nto sniff all RS-485 messages and use the sniffed message for replay attacks.\nThis weakness can be used to spoof the message \"quit alarm\" to continuously deactivate\nthe safe alarm.\n\n2) Insufficient Transport Layer Encryption on SafeController 65000 (CVE-2026-34022)\nThe SafeController Family 65000 is secured with weak and custom cryptographic\nalgorithms with hard-coded keys. An attacker who is in an adversary-in-the-middle\nposition can read and decrypt the data traffic.\n\n3) Undisclosed Vulnerability in the binary SafeController\nThis vulnerability was identified during a reassessment commissioned by Wertheim.\nDetailed disclosure is withheld as the finding is subject to the vendor\u0027s ownership\nand disclosure authority. Affected parties are advised to contact the vendor\ndirectly for further information.\n\n\nProof of concept:\n-----------------\n1) Lack of Cryptographic Protection on SafeController 5400 (CVE-2026-34021)\n```\nProof of concept removed because no patch will be provided\n```\n\n2) Insufficient Transport Layer Encryption on SafeController 65000 (CVE-2026-34022)\n```\nProof of concept removed because no patch will be provided\n```\n\n3) Undisclosed Vulnerability in the binary SafeController\n```\nProof of concept removed because of undisclosed vulnerability\n```\n\nVulnerable / tested versions:\n-----------------------------\nThe following versions/devices have been tested which were the latest version available\nat the time of the test:\n* Wertheim GmbH Safe Service for controller 65000 in AssemblyVersion 6.11.8130.22319\n* Wertheim GmbH Safe Service for controller 5400 in AssemblyVersion 6.11.8130.22320\n\n\nVendor contact timeline:\n------------------------\n2023-06-20: Initial meeting between SEC Consult and Wertheim to discuss\n            identified vulnerabilities\n2023-07-23: Contacting vendor through direct email addresses received\n            in the meetings, asking for encryption keys.\n2023-07-31: Vendor response to send advisory unencrypted and apologizing for delays\n            due to vacation time.\n2023-08-07: Sending two advisories (split between HW devices and SW issues)\n            to vendor, zipped with password.\n2023-08-07: Vendor response: project start in September, implementation\n            process planned to be finished early December. Estimation that\n            rollout of patches takes another quarter (end of Q1/24).\n2023-08-08: Meeting to discuss further steps.\n2023-10-13: Asking for status update via email; No response received.\n2023-11-30: Asking for status update via email - as no answer has yet\n            been received.\n2023-11-30: Vendor responds to our request with following information:\n            - Currently on time - Release plan Q1/2024\n            - A meeting between SEC Consult and Wertheim should take place in\n              Q1 to discuss further steps, including the recheck of\n              vulnerabilities.\n            - Updates are provided in different ways:\n              1. Customers with a support package receive the releases\n                 immediately\n              2. Customers without a support package receive an offer\n                 to upgrade.\n2024-02-16: Asking for status update and proposed dates for the planned\n            meeting in Q1/2024 via email\n2024-02-16: Vendor responds with following information:\n            - A recheck was arranged with SEC Consult to check the mitigations\n            - Recheck date planned for March 2024.\n2024-02-22: Vendor has submitted an internal project plan with information\n            and the status of ongoing remedial measures.\n2024-02-26: Meeting with the vendor to discuss next steps and recheck date:\n            - After the new review, the remaining weaknesses will be fixed and\n            everything will be rolled out to customers by September 2024 at the\n            latest.\n2024-03-05: Recheck date finalized for end of March.\n2024-03-29: Recheck conducted with the following results:\n            - Vulnerability 1: Not Fixed - No patch will be provided because\n              the controller is marked as End-of-Life (EOL)\n            - Vulnerability 2: Not Fixed - The algorithm was not changed.\n              Furthermore, it was possible to break the encryption and\n              decryption routine. It is possible to decrypt messages without\n              any knowledge of the encryption key. Furthermore, it is also\n              possible to gain knowledge about the encryption key by\n              intercepting enough messages.\n            - Vulnerability 3: New - Undisclosed Vulnerability in the binary\n              SafeController\n2024-06-17: Asking for status update via email; No response received.\n2024-09-25: Asking for status update via email.\n2024-10-10: The vendor responds to our request and informs us about the\n            following remediation status:\n            - Vulnerability 1: Cannot be fixed due to missing hardware support.\n            - Vulnerability 2: Cannot be fixed due to missing hardware support.\n            - Vulnerability 3: Fixed\n2024-10-18: Asking about the publication of new vulnerabilities identified during\n            the recheck, the version number in which the vulnerabilities were\n            fixed, and a workaround for unfixed vulnerabilities.\n2024-10-30: Coordination meeting regarding the questions raised.\n2024-12-16: Asking for a status update regarding version numbers. Sending\n            updated advisory with PoCs partially redacted. No response.\n2025-02-19: Asking for an update; no response\n2025-03-18: Asking for an update; no response\n2026-03-25: Sending final advisory to Wertheim for approval including a\n            publication date. No response.\n2026-04-23: Asking for a status update. No response.\n2026-06-11: Informing vendor about upcoming release.\n2026-06-15: Release of security advisory.\n\n\nSolution:\n---------\nThe affected HW controller 5400 is marked as end-of-life (EOL), hence there won\u0027t\nbe any patches provided by the vendor. The encryption algorithm for Controller 65000\ncannot be improved/fixed by the vendor as well because of missing hardware support.\n\nIt is recommended to assess the business risk and switch to a supported version in case\nany EOL products are used.\n\n\nWorkaround:\n-----------\nAs an interim mitigation, the following measures are strongly recommended:\n\u2014 Physically isolate all SafeController devices to ensure that only authorized personnel\n  can access them.\n\u2014 Harden all connected devices that communicate via the serial interface, including the\n  application of restrictive configurations and disabling of unnecessary services.\n\u2014 Ensure that servers communicating with the SafeController devices via the serial interface\n  are secured with strong, unique authentication credentials. The use of default, shared, or\n  weak credentials must be avoided. Access should be restricted exclusively to authorized\n  personnel with a legitimate operational need.\n\u2014 Ensure physical security of all interconnected components to prevent unauthorized physical\n  access or tampering.\n\nThese measures should remain in place until the vendor provides a verified and comprehensive\nremediation.\n\n\nAdvisory URL:\n-------------\nhttps://sec-consult.com/vulnerability-lab/\n\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nSEC Consult Vulnerability Lab\nAn integrated part of SEC Consult, an Atos business\nEurope | Asia\n\nAbout SEC Consult Vulnerability Lab\nThe SEC Consult Vulnerability Lab is an integrated part of SEC Consult, an\nAtos business. It ensures the continued knowledge gain of SEC Consult in the\nfield of network and application security to stay ahead of the attacker. The\nSEC Consult Vulnerability Lab supports high-quality penetration testing and\nthe evaluation of new offensive and defensive technologies for our customers.\nHence our customers obtain the most current information about vulnerabilities\nand valid recommendation about the risk profile of new technologies.\n\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\nInterested to work with the experts of SEC Consult?\nSend us your applicationhttps://sec-consult.com/career/\n\nInterested in improving your cyber security with the experts of SEC Consult?\nContact our local officeshttps://sec-consult.com/contact/\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nMail: security-research at sec-consult dot com\nWeb:https://www.sec-consult.com\nBlog:http://blog.sec-consult.com\nX:https://x.com/sec_consult\n\nEOF Gorazd Jank, Christian Hager, Philipp Espernberger / @2026\n\n_______________________________________________\nSent through the Full Disclosure mailing list\nhttps://nmap.org/mailman/listinfo/fulldisclosure\nWeb Archives \u0026 RSS: https://seclists.org/fulldisclosure/"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-09-11T07:55:56Z",
        "orgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
        "shortName": "VULNARCHIVE"
      },
      "references": [
        {
          "tags": [
            "technical-description",
            "exploit"
          ],
          "url": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jun/9"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://seclists.org/fulldisclosure/2026/Jun/9"
        },
        {
          "url": "http://blog.sec-consult.com"
        },
        {
          "url": "https://nmap.org/mailman/listinfo/fulldisclosure"
        },
        {
          "url": "https://sec-consult.com/career/"
        },
        {
          "url": "https://sec-consult.com/contact/"
        },
        {
          "url": "https://sec-consult.com/vulnerability-lab/"
        },
        {
          "url": "https://seclists.org/fulldisclosure/"
        },
        {
          "url": "https://wertheim-safes.com/safe-deposit-boxes/"
        },
        {
          "url": "https://wertheim.at/en/company/"
        },
        {
          "url": "https://www.sec-consult.com"
        },
        {
          "url": "https://x.com/sec_consult"
        }
      ],
      "source": {
        "defect": [
          "https://seclists.org/fulldisclosure/2026/Jun/9"
        ],
        "discovery": "EXTERNAL"
      },
      "title": "SEC Consult SA-20260615-1 :: Multiple Vulnerabilities in Wertheim SafeController Hardware for VAULT ROOMS (Safe Deposit Locker System \u2013 Microcontroller)",
      "x_gcve": [
        {
          "recordType": "analysis",
          "relationships": [
            {
              "destId": "CVE-2026-34021",
              "type": "related"
            },
            {
              "destId": "CVE-2026-34022",
              "type": "related"
            }
          ],
          "vulnId": "GCVE-1988-2026-0341",
          "x_vulnarchive": {
            "archiveUrl": "https://vuln.freearchive.org/archive/full-disclosure/2026/Jun/9",
            "automated": true,
            "contentSha256": "663969dbdbe4797525af1fc40d23cfa18bf8afe75fedfab2400a1580903cf95f",
            "evidenceScore": 9,
            "messageId": "",
            "originalUrl": "https://seclists.org/fulldisclosure/2026/Jun/9",
            "policy": "vulnarchive-1",
            "sourceFormat": "text/html",
            "sourcePublishedAt": "2026-06-15T12:07:16Z"
          }
        },
        {
          "recordType": "advisory",
          "vulnId": "gcve-1988-2026-0341"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "4e2abfbf-4a2a-4b76-a4e0-d77c18ba156c",
    "assignerShortName": "VULNARCHIVE",
    "datePublished": "2026-09-11T07:55:56Z",
    "dateUpdated": "2026-09-11T07:55:56Z",
    "state": "PUBLISHED",
    "vulnId": "GCVE-1988-2026-0341"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.



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.